Earlier quoted context omitted.
> I feel strikingly similar to the OP I'm glad you said that. If you feel comfortable doing so, could you share an anecdote? If a few people describe this from different angles perhaps more will come out of the woodwork and offer some solutions. I think the person you were replying to was gently suggesting to see a psychiatrist.
Sure. This is an extreme example. I'm just starting my third of university software engineering and I've been dreaming up a moderately ambitious (but technically straightforward) CRUD web app since early in my first year. Since then I've flipped and switched between countless frameworks and languages, shelved, reassessed, unshelved, reshelved, and scrapped many basic prototypes. Only recently I've made some progress…
Untitled topic
11–20 of 73 posts
Re: undefined
#12You need to speak with your doctor first. You may be out of shape, you may have a vitamin deficiency, you may have something complicated. The answer is in a doctor's office, not HN.
[deleted]
Diagnosing humans is pretty damn hard and will take time. Stick with finding a solution.
Re: undefined
#13Earlier quoted context omitted.
> I feel strikingly similar to the OP I'm glad you said that. If you feel comfortable doing so, could you share an anecdote? If a few people describe this from different angles perhaps more will come out of the woodwork and offer some solutions. I think the person you were replying to was gently suggesting to see a psychiatrist.
Sure. This is an extreme example. I'm just starting my third of university software engineering and I've been dreaming up a moderately ambitious (but technically straightforward) CRUD web app since early in my first year. Since then I've flipped and switched between countless frameworks and languages, shelved, reassessed, unshelved, reshelved, and scrapped many basic prototypes. Only recently I've made some progress…
https://en.wikipedia.org/wiki/Analysis_paralysis
The way out of it is just to pick something and see how far it takes you, accepting that you may have to backtrack and redo stuff in the future. There's this myth that experts got that way through good decisions; no, usually experts got that way because they made a lot of bad decisions really quickly and dealt with the consequences, and so now they know not to make them again.
Re: undefined
#14Check out: http://www.amazon.com/The-Motivation-Hacker-Nick-Winter-eboo...
Re: undefined
#15If others claim they could do the task faster, consider that programmers chronically underestimate.
If you've seen others do it faster, it's possible that they are taking shortcuts, making quicker decisions that will involve more work later. From your example, you've carefully picked a library and thought through how to integrate it properly into your code - these steps can be skipped for speed, but the cost usually isn't worth it.
There are always going to be better programmers, but they're often not the ones who claim to be great, or fast, or rockstars. So I'd just check to make sure you're not making unfair comparisons of yourself.
Re: undefined
#16Re: undefined
#17You may be chronically sleep deprived and not realize it. If that's the case you should try sleeping really consistently for a week and check the difference. Don't use an alarm, just be really disciplined about going to sleep early enough to wake up naturally. No caffeine or other stimulants. The difference between a well rested brain and a sleep deprived one is night and day.
When I don't get 8-9 hours of sleep, I code exactly the way OP described. Things that normally take an hour, take a full day because I can't focus and miss the most embarrassing, basic stuff.
Re: undefined
#18Earlier quoted context omitted.
> I feel strikingly similar to the OP I'm glad you said that. If you feel comfortable doing so, could you share an anecdote? If a few people describe this from different angles perhaps more will come out of the woodwork and offer some solutions. I think the person you were replying to was gently suggesting to see a psychiatrist.
Sure. This is an extreme example. I'm just starting my third of university software engineering and I've been dreaming up a moderately ambitious (but technically straightforward) CRUD web app since early in my first year. Since then I've flipped and switched between countless frameworks and languages, shelved, reassessed, unshelved, reshelved, and scrapped many basic prototypes. Only recently I've made some progress…
Let's go to the redoubtable Yegge and his concept of "Shit's Easy Syndrome":
http://steve-yegge.blogspot.com/2009/04/have-you-ever-legali...
Stick with it. The set-up is long, but it pays off handsomely.
Re: undefined
#19I think another question to ask yourself is, why do you feel this isn't normal? If others claim they could do the task faster, consider that programmers chronically underestimate. If you've seen others do it faster, it's possible that they are taking shortcuts, making quicker decisions that will involve more work later. From your example, you've carefully picked a library and thought through how to integrate it prope…
Also consider that they may have used that library previously.. so you don't get to see them spend a whole day making mistakes with it and trying to get it working.
Re: undefined
#20If you are writing your own, it should take more than a day. You can't just slap it together and expect it to be right. That's why there are companies like Stormpath.
What you probably need to do is work on building some reusable library of personal code so that you can get shit running faster. Base it off one of the major frameworks and just make some boilerplate projects that you can check out and get up and running fast. Try to reuse code. You don't have to write reusable modules to reuse your code. Just have a skeleton project that makes things faster.