logoalt Hacker News

lnenadtoday at 5:12 PM6 repliesview on HN

As a /senior/ developer I really dislike blanket statements. I've seen the same amount of failures caused by

> “Do we really need that?” > “What happens if we don’t do this?” > “Can we make do for now? Maybe come back to this later when it becomes more important?”

as with experimenters. Every system is different, every product is different. If I were building firmware for a CT scanner, my approach towards trying out new things would be different than a CRUD SaaS with 100 clients in a field that could benefit from a fresh perspective.

There are definitely ways to have eager/very open seniors drive systems into hard to get out corners. But then there are people that claim PHP5 is all you need.


Replies

bilekastoday at 5:59 PM

I came to say somethign simular actually.

> Ah, baby, this is my senior developer. The avoider, the reducer, the recycler. They want to avoid development as much as they can.

There are times when this is good, there are times when actively trying introduce an improvement is the best way forward. A good senior is able to recognise when those times are.

show 2 replies
hirako2000today at 5:23 PM

A sort of survivor bias. A VP ordered to use elastic search, because it worked well at his company before. Turned out it worked well for us. Listen to the VP to make technical decisions. And use elastic search.

show 2 replies
sisvetoday at 6:55 PM

Agree. context matter. As a senior developer you need to understand complexity, risk, upsides and and downsides. Understand the business side. If you are a startup or a big company that is already a cash cow makes a difference when changing a core featrue of the product etc... context context context

show 1 reply
lwhitoday at 6:33 PM

I think you may be missing the message the OP is trying to communicate.

The qualities were highlighted because they can all lead to better stability.

show 1 reply
someone654today at 7:07 PM

Was thinking the same thing, but then i re-read the section and noticed this:

> Yes, yes, of course this is simplistic.

It's an example, put to the extreme, to clearly communicate the ideas. As all things, the golden mean applies, as I understand the article argues for:

> the design of the 'Scale' version is influenced by what worked and what doesn’t work in the 'Speed' version of the system.

dickywadtoday at 6:52 PM

[dead]