Hang on a minute. I'm both Superprogrammer and a washed up old has-been? This is getting confusing.

There's no shame for me in using integration tests. They just hint at an alternate universe where the design is different and they either disappear entirely or become unit tests. So today isn't the day that happens. Okay. "Perfect" is a verb.

I'm struggling to understand how the transition from integration test to unit test might manifest in terms of a real world refactoring.

My 'integration tests' almost always cross the boundaries of two or more (theoretically) well-defined APIs. If they're within those boundaries, well, they're not really integrating anything, so I would just consider them a unit test.

Do you have any examples of this?

There's a challenge finding the right headline when posting to HN. My last few posts had very literal headlines and went nowhere. I amped this headline up a bit while making sure it was still honest and, looky here, it got more attention. Now I have to decide how I feel about the difference.

FWIW, it doesn't bother me. Perhaps phrasing amped-up headlines as questions would forestall at least the more moderate wing of the clickbait squad?

Thank you for letting me know how I appear to you. I don't agree that my point of view is obsolete or that I am not entitled to an opinion about design. Judging what I write based on my age led to you, as other commenters have pointed out, missing the point of my post.

Your point about up-to-date examples is well taken. Finding good examples is the hardest part of technical writing for me. As I work on Facebook and Instagram I will keep my eyes open for clear examples of the same principles, because the principles really are the same regardless of shifts in technical fashion. You'll have the opportunity to learn that in the years to come.

How is this a disagreement?

If you don’t categorise it as one I guess we’re good. :)

Following the drip down the canvas is as important as moving the brush along (to stay with the metaphor).

The invasion of Iraq is what I had in mind. I wanted to point out the senselessness of that operation.

My skill/specialization visualization is the paint drip model (generalization of T). You're adding a little of this skill, a little of that, one catches your eye and you dive deep for a while, then a little of this, a little of that.

I assumed that readers had one strong skill already, hence the emphasis on broadening.

I updated the description of 80/15/5, a career risk management strategy.

Several of these have been suggested to me by mentors, many others are new. This is a fantastic list. Thank you for your thoughts and advice.

About this item, I got me wondering: Should we never delegate a difficult work for someone that is specialist if it give us pleasure? Always we need to learn it first?

I don't agree with this, maybe I need profit instead of fun. I can found fun in a lot of other things that I can't delegate on moment.

Sorry if I am misunderstanding this part.

typo: "Beauty if a powerful […]"

tl;dr You can make content so bad that it won't spread, but you can't make it so good that it is certain to spread. Virality grows at the confluence of skill, timing, and luck. Be aware when you've hit the point of diminishing returns on quality and publish.

There is a big difference between "I'm polishing this because it will have a higher viral coefficient", or "I'm polishing this because I am learning by polishing", or even "I'm polishing this because it feels good to polish" on the one hand and "I'm polishing this because I'm afraid of the feedback I'm going to get on it once it's in the wild" on the other. My polishing falls more often in the latter camp so I look for ways to counteract my bias. If your polishing really really makes a difference, then heavens to betsy be my guest.