5 ms·
Doing something a second time is almost always faster. You can’t draw any information from this, except perhaps that the author avoided Second System Syndrome.
by hinkley 5y ago
Doing something a second time is almost always faster.
You can’t draw any information from this, except perhaps that the author avoided Second System Syndrome.
In college I worked with students who had programming jobs. While my classmates were spending fifteen+ hours on assignments, one of these coworkers who I shared a class with said he was spending two hours and I thought he was lying. Another was claiming three or four. This must be bravado I thought.
Next summer I got a programming job too. That fall I was spending six hours on homework, and by year’s end I was down to three.
When everything is new you go slow. You have to solve problems without muscle memory, and you have to fight nervousness. Am I doing this wrong? Is this even a good answer?
They talk about 10000 hours and mastery, but there are also clear breakpoints at 100 and 1000 hours, where you know enough to do a lot, and you don’t have to stop to consider your first moves.
- MarkLowenstein 5y agoWhen something becomes routine for a developer, where they can predictably finish a work item without designing anything new, that task is immediately flagged in managers' minds as one that should be done by a more-junior/contractor/3rd-party/off-the-shelf solution. Almost by definition, then, good developers are relegated to only doing tasks that they are doing for the first time. The implications of this natural law are evident in the quality of the output, the predictability of the schedule, and career burn-out of people who are asked to be creative 100% of the time.
- hinkley 5y agoI still spend a lot of my time manipulating lists. Although it may be fair to say that experience helps you realize that you can turn some problems into manipulating lists. Easier to write tests for, and for the next person to understand. The problem, from the manager's standpoint, is that the really good solutions are simpler than the really bad solutions. That may not sound like a problem, but the concise, correct answer is often self-evident in retrospect, diminishing the gravity of the situation. Lots of people make suggestions you instantly agree with, but you would not have come up with all of those suggestions on your own. A bad boss won't understand that, until you make another self-evident decision that you would get more money and respect working somewhere else. Maybe not even then.
- xmprt 5y agoI think doing things for the first time is still something you can get better at. Although you're working on brand new problems all the time, you can still improve at skills like digesting the problem, splitting it into subproblems, designing systems, faster implementations and testing.
- karmakaze 5y agoI wish this was true. I'm always finding myself moving around in an organization and projects trying to find new challenges rather than building another standard API. Certainly every project has it's critical pieces where any extra attention can pay off but not so many.
- MarkLowenstein 5y agoWhat type of company do you work for? It may be different in software/services vs. commerce companies.
- karmakaze 5y agoI actually work at a software/services company for commerce. Don't get me wrong, this is a big space and there are many challenges but they often tend to be more vertical than technical. Lately I've been making a monolithic app behave less so with decoupled async notifications. Also spend some time prototyping things for future adoption for if/when that's feasible. I'd like to be using something functional like F# but for some reason not being in adtech/fintech drastically lowers tech appetite of companies.
- fijiaarone 5y agoI think a trick you can learn here is that once you're good at doing something that is difficult to do the first time, and becomes tedious to do on repetition -- but is still something that needs to be done frequently, the way to vastly increase your value is to be able to teach others how to do that thing.
- legulere 5y agoAlso between the first and the second time you have plenty of opportunity to plan ahead for what you are going to do differently next time.
- hinkley 5y agoYes, but that's the trap of Second System. You can have too much time to plan and you end up with a baroque nightmare that everyone resents, including (eventually) you.
- jimbokun 5y agoMy son was taking his first programming course, and was watching him working on an assignment. He was running the compiler and executing his program in the terminal. I mentioned to him: "Did you know you can pull up your past commands by hitting up arrow?" His mind was blown. I think that comment doubled his productivity.
- Jtsummers 5y agoAnd the next lesson: C-r will search the command history (at least in most *nix shells). So when needing to do something but you aren't sure how far back it was (not on the screen or not recallable) but you know it is in the history and some text in it, just C-r <something> [C-r repeatedly until you get to the correct version].
- TaurenHunter 5y agoGreat tip! I've found more like that at: https://www.redhat.com/sysadmin/cli-speedup https://www.redhat.com/sysadmin/cli-speedup
- mindcrime 5y agoRelated trick: type the first couple of characters of the command in question, and hit PGUP until you find the correct version.
- nitrogen 5y agoThis one's my favorite. Not every distribution of readline enables this, so you might need to uncomment or add the binding for history-search-backward/forward into /etc/inputrc or ~/.inputrc. Similarly editrc for programs that use libedit instead of readline to avoid the GPL.
- cogman10 5y agoJust as useful, history | grep pattern With all the useful grep abilities (like peaking at commands before or after the given pattern).
- josephg 5y agoThere's a few other variants of this: When I was a TA marking assignments I saw a huge range in the number of lines of code between my students' assignments. If I took all the students who got full marks, there was often a 2x or 3x size difference between the smallest submission and the largest. And the large assignments didn't look bloated. If you gave me the code from a random student, it wasn't obvious where in the size range their code would land. And a couple years ago I worked as a professional programming interviewer. One of the assessments we did was a half hour programming problem. I interviewed over 400 interviews. Most of them had some professional experience as software engineers. Candidates use their favorite language and their own computer & tools. Quantitatively, there is a massive difference between the better candidates and the worst. The strongest candidates could get about 2-3x as much done in the same amount of time as the average. And the weaker candidates (even those with professional experience) could barely implement hello world within half an hour. As software engineers, we don't have a culture of practice. Its assumed that with enough time working professionally, we'll keep improving. But that might be naive. There are almost certainly ways to measure our skill and improve over time. Its weird we don't even have that conversation.
- urthor 5y agoWe do now though? A large chunk of the industry is obsessed with doing binary tree traversals for paycheques.
- ZephyrBlu 5y ago> As software engineers, we don't have a culture of practice. Its assumed that with enough time working professionally, we'll keep improving Man, this is exactly what I've been thinking lately. I don't have that much professional experience and have a background of competitive gaming where there is a really strong culture of explicit practice. Coming to software development where people with a lot of experience can't articulate their process or the steps they took to improve is really fucking annoying. I don't expect a step-by-step manual, but I do expect something instead of it all being tribal/intuitive knowledge.
- wtetzner 5y ago> Its assumed that with enough time working professionally, we'll keep improving. I’ve heard this described as “10 years of experience” vs “1 year of experience 10 times”.