Live data from Hacker News

Engineering "home-cooked" software

ownerofhappy.org

31–32 of 32 posts

Re: Engineering "home-cooked" software

#31

This feels like someone who hasn't been in the industry long enough to know what it is like to try and design software before implementing it with groups larger than 3, and yearns for problems that aren't as complex as the ones they are dealing with. It is easy to build "home cooked" (by his definition) software when you are building for a small number of people by a small number of people. Old Visual Basic programs…

I used to beat myself up about not writing much solo software. But the truth is I write little tools at work all the time, and those are almost always solo until I get buy in from others. I also introduce a lot of new or modified processes.

I just don’t sit at home writing more code very often, except to fix bugs I saw at work, or as interviewing prep.

But there was an article here recently that proposed a negative correlation between solo projects and teamwork. And that kind of explains a lot. People who wander off and do large things alone tend to be my more antisocial coworkers. Though I do occasionally see it from socially awkward coworkers who seem to want to be more engaged.

Writing software for other people without talking to them about it is kind of a weird plan.

Re: Engineering "home-cooked" software

#32

I couldn't disagree with the premise of the sections more on development methodology > Fast Food > Here, we develop in "agile" sprints. Working software is developed at the fastest pace possible, and all bugs are to be fixed later. > Home Cooked > Here, things are slower, more thoughtful. More waterfall-y. While Sprints is a term that sounds like fastest pace possible, that is not what the term means; and a key part…

Oof. I hate when people torture analogies.

There are for instance much better allegories for performance programming in the notion of an apple tree than “low hanging fruit”. Picking the low hanging fruit is just as wasteful a process in both domains.

Fast food restaurants don’t prepare food when you order it. It’s already mouldering in the back. They only make it on demand if you make a special request or they already fucked up their inventory estimates. It’s a lean process not an agile one.

And if you don’t think real restaurants sprint, maybe you should watch The Bear.

Post reply on HN