Lack of sleep, have a young child at home ... can't really focus on anything else but documenting own older code or watching lectures right now.
Been through this and in retrospect this was a blessing in disguise. Instead of sitting down and writing a draft code version, then reworking it, then reworking it again, then realizing there's a better way to do/structure the same, discarding it and making a clean version I was forced (by the baby-centric lifestyle) to think it all through in the head first. I would then sit down and emit the final version on the fi…
Ask HN: Why aren't you coding?
301–310 of 316 posts
Re: Ask HN: Why aren't you coding?
#302Earlier quoted context omitted.
> I'm sure a lot of people have this problem: naming things. Can't code until you figure out what that variable should be called. i, j, k, foo, bar, baz, and don't waste a moment thinking about it till your solution is finished and warrants a once-over (or till it has grown sufficiently complicated that a real name is finally necessary even if temporary -- try to work in small enough units that this never happens).
I generally think that if I can't find a good name for a thing, I don't actually know what it does yet, so Im not ready to code it. I, j, and k have clear definitions as basis vectors, so they can be used, but I don't think I'd ever call a variable foo or bar
I can understand that viewpoint. On the other hand, you have to develop that understanding somewhere, and on some problems I find that sketching out a solution in code is more productive than using a whiteboard or some other mechanism, especially if I already have a rough idea of what needs to happen.
E.g., I might know that I need to keep around a little intermediate state, and I'll throw that in an unremarkably named variable and iteratively build up the rest of the algorithm. Once I have _some_ solution I can go back and see if the variable was really important, prove it correct (or find additional work to do), and dole out meaningful names.
The idea isn't that different from how when building up something which needs a loop you might start with "while (True) {}", figure out where you need to break, and then go back and factor in an appropriate stopping condition once you understand exactly what the loop needs to do to accomplish your goals.
Re: Ask HN: Why aren't you coding?
#303Earlier quoted context omitted.
Came here to say this. Coding is one part of the job but mostly what I get paid to do is solve problems. I've worked on projects that were more process oriented and produced zero code whatsoever and still had the sort of outcomes good software does. The vast majority of my job, outside of writing efficient and secure code, is learning about other systems and domains. Software Engineers can be employed in anything fro…
I’d love to hear about a project that produced zero code. I can’t even imagine it outside of compliance or regulation maybe.
Re: Ask HN: Why aren't you coding?
#304Earlier quoted context omitted.
You aren’t writing up UX requirements. You’re writing system designs. If you’ve never had to write down and get feedback on a system design that is entirely okay, but as you work on projects of increasing complexity and scope, it becomes more and more important to plan before you write. The prototypes you’re describing are primarily useful for UX iteration, not system design.
A short system design doc with a working prototype is vastly superior to a 50 page design doc with no code. Think of it as the scale model of the house in the original example. It’s a way for sake holder to see and feel what they’re going to get.
Abridged and abstracted documents add their own confusion.
Re: Ask HN: Why aren't you coding?
#305Earlier quoted context omitted.
Perhaps. But methodology should be independent of being able and willing to ask questions. A close colleague recently left a company because the talk was "we're agile" but the walk was "don't ask questions, just do what you're told."
> But methodology should be independent of being able and willing to ask questions. What if asking questions significantly increases quality and productivity? I mean, strictly speaking, Agile is no methodology but more a set of values [1], that defines a culture rather than a methodology. Yes, there are agile methodologies (Scrum, XP, etc.), but those are worthless without the right culture. In fact, I think you are…
Culture either allows and values questions and improvememt or it doesn't. If it doesn't then methodology will not override (read: fix) that.
Waterfall or not, or otherwise isn't really relevant. Culture is.
Re: Ask HN: Why aren't you coding?
#306Because I’m having an existential crisis thinking how incapable I am and have been winging it all along. Keep stressing over how long would it be before they find out and kick me out.
Re: Ask HN: Why aren't you coding?
#307I'm being paid whether I write code or not, so there is that.
Re: Ask HN: Why aren't you coding?
#308I'm burnt out. I've been on sick leave for over half a year now. Luckily I am in a country where I am protected, but I'm receiving less salary as the law indicates. I'm trying to focus on the good things in life. In my downtime from work I've tried to start a few personal projects, but I just can't seem to stick with it and I end up just playing video games all day. I just wanna crawl into the fetal position and die…
Re: Ask HN: Why aren't you coding?
#309I know ultimately I want my own product. A simple, niche, probably boring, product that myself and my wife can maintain, and ideally - pay for our living expenses. That's the big shiny goal.
My agency (of 8 years) was acquired late last year, and I'm currently a little burnt out. I have so many ideas, a smattering of self-doubt, and I think deep down a bit to prove to myself.
So at the moment i'm taking a break, and focusing on something a bit left-of-centre (for me at least).
I am writing all my experiences of starting and running a software agency up at https://devtoagency.com . It's oddly cathartic, and as somewhen who has never written before I am finding it a mixture of fun, exciting, nerve-wracking and again - sometimes self-doubt inducing.
For the first time in my life I am also part of a community (on Twitter). I am conversing, and helping new developers, and it feels good... It's not all about "me", and I think that's what I need this minute.
This just turned into a weird self-help exposé ;)
TLDR; I am focusing on helping others through writing and community building.
Re: Ask HN: Why aren't you coding?
#310Earlier quoted context omitted.
Why do you have to ascribe good practices such as confirming work necessities as being “Agile” or not? The word (as a proper noun) to me has lost all meaning having been inane different workplaces, all of which claim to be “Agile”.
I've also witnessed agile being used as a excuse for "We're not going to take the time to understand the problem. We're not going to work with the client so that they understand their own problem. Nah. Insted, just do the work. Do what you're told. If we miss the target we'll fix it in another sprint. They're paying. NBD."