7 ms·
There's feeling like you're getting things done because you're on a coding roll, and then there's feeling like you're getting very little done because you're st
by lordnacho 9y ago
There's feeling like you're getting things done because you're on a coding roll, and then there's feeling like you're getting very little done because you're still organising the project in your mind.
I don't think the two can be separated. Being stuck and being moving are dependent on each other.
A lot of the time I'm frustrated because I haven't quite figured out how the code should look. It takes a long time, a lot of chopping and changing, before you come upon a structure that you feel comfortable building on.
When you do get to that point though, it feels easy. Everything you write makes sense in terms of your new structure, and there aren't so many awkward kludges. The only thing is this period can be brief, because when you're fast, you get to the next problem sooner. You'll find higher and higher levels at which to view your code, and at each level you'll need to do some organising.
- amelius 9y ago> Being stuck and being moving are dependent on each other. Yeah, but in times of being stuck, it's much easier to get distracted and procrastinate.
- david-gpu 9y agoSome amount of distraction is probably helpful. Once you have gathered all requirements and have thought about the problem for a while it is good to let it marinate for some time. You will often have moments of insight seemingly out of nowhere while you are e.g. going out for a walk.
- 18nleung 9y agoAgreed. I often figure out a solution to a problem I'm having as soon as I stand up from my desk!
- matwood 9y ago> Yeah, but in times of being stuck, it's much easier to get distracted and procrastinate. A bit, but I tend to do directed procrastination. Go the gym, do some research on a different problem, write some emails, etc... As soon as I stop actively thinking about the problem a solution will come. Another solution (and this works well with coding and writing) is just to start coding/writing. I'm writing an article now for a newsletter, and the top of my document is a bunch of stand alone sentences that eventually lead to a full article. In programming, I'll often do the same thing and just start solving the problem even if I know it's not the right solution yet. Usually this leads me to a better understanding, and eventually the solution.
- jansho 9y agoDirected procrastination works for me too. I usually hate admin type of work; sorting out my room, doing the laundry, responding in social media (yes, that counts too..) But when I hit the inertia part of the productivity cycle, this saves me. It's always better to do something than just being stuck. And while I mechanically do those tasks, my head also gets in order, I start dreaming and slowly, I'm on the roll again. When the right time comes, I slide back into the 'real' work. I can't quite regret for 'wasting' that time, because usually the reward is a new perspective, and the ideas that come with it. Shrugs, we're not machines.
- corysama 9y ago> As soon as I stop actively thinking about the problem a solution will come. The book 'Hare Brain, Tortoise Mind' has a good explanation of how that works, what it's good at and what it's not. I get a lot of side chores done with directed procrastination. But, what works for me to get the main task done is to just open the IDE even without a goal. Instead of "Ugg... I need to make X work today...". Just open the editor and do anything. Refactor a function. Comment something. Whatever. Once you get started, it much easier to continue.
- krallja 9y agoMy problem is when I open the editor and refactor a function, I start finding other functions that need to be refactored, then finding even more refactoring opportunities from those, recursively, forever. At some point I need to stop refactoring and start producing something new...
- travmatt 9y ago> Steve McConnell in Code Complete (a book which criticizes the widespread use of the waterfall model) refers to design as a “wicked problem” – a problem whose requirements and limitations cannot be entirely known before completion. The implication is that it is impossible to get one phase of software development “perfected” before time is spent in “reconnaissance” working out exactly where and what the big problems are. https://en.wikipedia.org/wiki/Wicked_problem https://en.wikipedia.org/wiki/Wicked_problem
- everyone 9y agoI used to be an architect before I became a programmer, so since I started programming I noticed I hag a big advantage over my peers when it comes to the high level designing and structuring a program. Thing is, the more experienced I become at programming, the less of that I end up doing. I more and more tend to break everything down into tiny parts that can all work independently and be composed into bigger bits. Most of my career I've used OO languages, especially C#, but nowadays I usually avoid using a lot of the features of OO, like inheritance, and just try and make everything from tiny little methods (functions) big things are just made from several of those methods in sequence and really big things are just made from several of the big ones. From a development perspective it means I can just go ahead and start writing useful little snippets of code and start composing them together into bigger and bigger features as I go. So, I'm switching from a top-down style to more of a bottom-up one.
- eru 9y agoIt's always interesting to me to see how various people discover the basic advantage of function-oriented programming on their own. There's also eg the copy-on-write filesystems, and git---whose main on-disk data-structures are conceptually immutable despite being implemented in C. You might enjoy reading "Out of the tarpit" (https://github.com/papers-we-love/papers-we-love/blob/master/design/out-of-the-tar-pit.pdf https://github.com/papers-we-love/papers-we-love/blob/master...), a paper that deals with approaches to master software complexity.
- deleted 9y ago
- dasmoth 9y agoAgreed. And I'm increasingly tending to think that the stuck-thinking-about-the-tricky-stuff phase is the part of the game I find most satisfying. A lot of textbook management techniques seem hellbent on trying to force steady productivity instead of punctuated equilibrium. Not the recipe for a satisfying environment.
- GuiA 9y agoI once had a manager ask me to email him a progress report every day; and every hour or two, he'd make a point of interrupting me to ask me "so how's <current_task> going?" Sounds like something straight of office space, but that was my life for a while. Least productive job I've ever had because of that (well, and the myriad other little toxic/passive aggressive behaviors he had). He had a Stanford MBA too, which convinced me of how useless MBAs must be. Because if you make it through one of the top programs in "business administration" in the world and still manage like that, you might as well have an MD from Harvard and still believe bloodletting is a viable treatment for illnesses.
- Alysha3434 9y agoI get paid over $95 per hour working from home with 2 kids at home. I never thought I'd be able to do it but my best friend earns over 10k a month doing this and she convinced me to try. The potential with this is endless. Heres what I've been doing, https://www.youtube.com/watch?v=gfJ3KWPnqqs https://www.youtube.com/watch?v=gfJ3KWPnqqs
- dasmoth 9y agoI once had a manager ask me to email him a progress report every day; This seems to have become very nearly normalised in the guise of daily stand ups. Some would argue it's less intrusive if it's for "the team" rather than for an individual manager, but I'm not convinced myself. and every hour or two, he'd make a point of interrupting me to ask me "so how's <current_task> going?" Similarly, in environments where tasks are getting broken down into tickets that are only expected to take a few hours, there's a similar level of oversight (although hopefully a bit less disruptive than hourly shoulder-taps, I agree).
- BurningFrog 9y agoThe thing I find works better than anything else is to write some code that works, even though I know it's far from the "right" design. Once you have concrete working code, it's much easier to organize it in ways that make sense than trying to visualize everything beforehand. As a young programmer I was taught to carefully design code before starting to write it. It kinda blows my mind that now I design it after writing!
- stult 9y agoThat works for me too. I'm originally a lawyer and a decently competent writer and that's also how I approach papers or briefs. Writing is how I think and organize my thoughts so there's no more efficient way for me to design an overall architecture, whether in code or English, than just by starting to write. Once I start to get a grip on the parameters and pain points, I'll circle back and outline the higher level. My brain just works better from a bottom up starting point. Writing and coding are just formalized ways of thinking so sometimes you have to make concessions to your own brain's idiosyncrasies.
- convolvatron 9y agobottom-up is hardly a shameful idiosyncrasy. top down has a tendency to fail by imposing an inappropriate structure, and missing important details. every discussion i can remember ends up recommending switching directions repeatedly. i start on the up-stroke myself, always worked for me
- BurningFrog 9y agoYeah, I write a lot that way too, probably influenced by my programming habits. I read somewhere that Neil Gaiman considers himself only a decent writer who is an extremely good editor. Which is to say, he starts writing a simple draft, and then changes what's wrong with it, over and over.
- graphitezepp 9y agoThe trick to this model is being good enough at figuring out your organization of code that when you get to the easy part of implementation, you don't happen to discover you made a bad assumption earlier.