101–110 of 180 posts
The resistance stage that you've hit is always a killer. It leaves more projects like yours dead before they're finished than anything else. The problem with replying to this, is the answer is subjective and will vary person to person. We all use different methods to motivate. Sometimes I'll re-read a book. Masters of Doom is motivational for me as one example. Sometimes I'll take a long'ish break (weeks) and teach m…
You don't need 'motivation' to put one foot after the next. It's 99% 'perspiration', remember? If you care about the outcome (whatever it is) then that should be enough 'motivation' to do the 99%. You're a professional, right? If you want a 'purely motivational' project then do something that's simply that: games, writing/playing music, reading etc., where 'it doesn't matter'. Instead of trying to 'find motivation',…
Earlier quoted context omitted.
This is the 'it's too cold outside' runner's trick for motivation. If it's very cold outside, you tell yourself 'if it's too cold after 10 minutes I'll come back in'. But you never come back in. It's a matter of getting started, nothing else. We are funny creatures.
That never works for me: after 10 minutes of running, I'd be thinking things like "Is my 10 minute rule really meaningful if I don't REALLY allow myself to quit after 10 minutes? I should quit today just to reinforce to myself that the rule is really meaningful.". Then, next time I run I have exactly the same thought and the whole concept falls apart.
I used to always want to quit running ASAP, and the feeling just didn't go away whether I ran for five minutes or an hour. Fast forward some years, I'd gotten into cycling, enjoyed my rides and was in a much better physical condition. I also had a heart rate tracker and was used to training with heart rate zones. So one time I went for a run, first time in years, and tried to stay in the I gather this is a common phenomenon, and most beginners run way too fast.
It's simple - stop trying to right prefect code because it doesn't exist. Next, go sell it. Building a company means creating a balance and from what I hear, it's one sided; software development. Get people using it. Get people to give you feedback to drive the features, Engineers typically suck at sales and get caught up in building. Release it. Your customers don't give a shit about the code. I know you do and I re…
We dont per-say have projects, we have jobs (but theyre similar!) we took on overhauling every school bus for the largest city in the state. Its a tip to tail job that takes about 1500 hours per vehicle.
Our upholstery subcontractor sucks. They work largely for RV companies and either have a hard time procuring seat fabric, or a hard time hiring anyone who can reasonably upholster seats 8 hours a day. Theyre based out of florida and so arent used to working in cold midwest weather.
brake upgrades take ages because these are midsize trucks and we're going through tooling fast on turning rotors. management doesnt understand this at all, and so constantly drags their feet having to order new carbide inserts.
my motivation is for what comes after we're done. its the need at the end of the job that keeps me going. new steering, heaters, and seats all make for safer buses for kids and professional drivers. I guess find out what youre doing and why youre really doing it. put yourself in touch with the people who use this software and spend a day in their shoes.
When I read "Go SDK" I wonder if there are better SDKs in other languages from this provider. I often find that although they advertise having 10 different SDKs in reality only one or two actually work while others are just a badly maintained afterthought. Happens a lot to us .NET users. I find it better to write the code parts that deal with the SDK in one of the premier languages and then integrate this into my cod…
Earlier quoted context omitted.
I should try contacting support; thanks. Some of the weird things I've run into are so poorly thought out that I can't believe they'd actually be an intentional part of their product. I've talked to some developers on their IRC channel, but typically (and this is something I strive as hard as possible not to do on my own projects), they were just so used to it that they couldn't understand why anyone wouldn't know ho…
I've worked with quite a few payments platforms over my career. Most of them are terrible, but even the good ones require adopting their conceptual model. Sometimes that can require some adjustment, especially if you already have preconceived notions of how you want billing to work. Example: I was dumbfounded that Stripe lets you update a balance, but offers no way to do it atomically. Support was clueless. However,…
One day, you will be dead. Each year that passes after your death, fewer and fewer people will remember who you were, what you did or what your face looked like. Eventually, you'll be completely forgotten. Who cares if that side project you put out sucked or not. Might as well put it out there and see what people think. There's a good chance too that the project won't even be remembered even by the time you die. The…
I usually like to save my existential crises for later in the week, but thanks for helping me dive right into it on a Monday morning.
One day, you will be dead. Each year that passes after your death, fewer and fewer people will remember who you were, what you did or what your face looked like. Eventually, you'll be completely forgotten. Who cares if that side project you put out sucked or not. Might as well put it out there and see what people think. There's a good chance too that the project won't even be remembered even by the time you die. The…
That line of thinking can also be quite demotivating. For instance, it could also be used to argue that since none of what I do matters anyway, I might as well spend it doing something else such as watching TV, playing video games, hiking in the forests, reading a good book, etc.
What makes you say that?
Is what you’re doing now worth doing only if people remember it after you die?
Family, friend, partner, coworker, even random stranger at the bar or a meetup.
Showing what you've made to someone is so much different than trying it yourself.
* The strange UI choices you made will be pointed out
* You will feel embarrassed about the slow loading of something
* You will get questions that you never thought about, and questions you thought about but perhaps thought nobody else would care about.
In my case, I'll always get motivated to do something with a project after I show someone else.