Live data from Hacker News

Senior engineers are living in the future

zerobanana.com

51–60 of 241 posts

Re: Senior engineers are living in the future

#51
post #8

Senior means two things: - Have experience - Self learning though above experience. I met many experienced developers, but most of them failed at step 2. To me, they're still junior.

I think you can be senior without experience. To me, senior means "can handle ambiguous/incorrect/incomplete problem definitions."

Re: Senior engineers are living in the future

#52

Earlier quoted context omitted.

Can you give an example of a failure at step 2?

A 10 years Java/PHP developer doesn't know how to use Golang on the job in 3 days.

I'd give them 1 week. And measure again at starting of week 3, if they are still struggle, that's very likely they suck at learning.

Re: Senior engineers are living in the future

#53
Not an engineer, but I find this translates well over to design.

Seniority in a lot of ways feels like the acknowledgement of being able to utilize people/soft skills in order to build things. I find at least 1/3 to 1/2 of my time, a roadblock in the project is caused by accidental miscommunication from top down, and the faster you can debug those, the happier everyone will be.

Personally I rather enjoy that hybrid of people and "hard" design, but it's definitely not for everyone.

Re: Senior engineers are living in the future

#54

Earlier quoted context omitted.

A 10 years Java/PHP developer doesn't know how to use Golang on the job in 3 days.

I learned it in 2 hours so you are pathetically junior compared to me.

I can figure out its internal AST once I stare at the lang's codes. \s

Re: Senior engineers are living in the future

#55

Earlier quoted context omitted.

A 10 years Java/PHP developer doesn't know how to use Golang on the job in 3 days.

I would never fault someone for not being able to pick up a language and use it competently in 3 days. I understand why you use this as an example, with having samey syntax, but there is still nuance. I think the bigger indicator is you've been in the industry for 10 years and call yourself a PHP/Java dev. At this point you should have dabbled in probably 10-100 ways of solving problems depending on what your 9-5 loo…

Same. I've never seen anyone become proficient in a new language/platform in less than a year. Sure, you could learn Go's syntax, use it in the style of Java/PHP, and make it work, but that is not being proficient in Go and its idioms.

Re: Senior engineers are living in the future

#56

Earlier quoted context omitted.

Who said you need competence, looks like that was your own insertion, haha. But seriously is it not unreasonable to be able to write some non-deep dive code in a new but similar language in just a few days? 3 days is a long time to read and ask questions.

What purpose does it serve though? I think being able to read and understand a Go program is a better example. That does seem like a reasonable and useful ask in 3 days for a veteran PHP/Java dev, and something that is more likely to come up in practice. What is the context of the former? "Welcome to our team. I know we didn't hire you as a Go dev. You have 3 days to "be able to write Go". I have long subscribed to "…

If you hire someone in a language they don’t know, you expect them to learn on the job. It’s reasonable by day 3 to expect them to show some code - even if terrible.

Re: Senior engineers are living in the future

#57
post #28

Earlier quoted context omitted.

A 10 years Java/PHP developer doesn't know how to use Golang on the job in 3 days.

In other words you're inventing some silly criteria that I'd guess you'd pass that others wouldn't. What I would say to that is that if you dismiss someone else's experience because they can't do some task you think they should be able to do rather than understanding that their experience probably brings something else to the team then that's your failing, not theirs. For a little annecdata - I've been a dev for 25 y…

Also importantly, it sounds like you would bring the understanding that surface level productivity is not the same thing as mastery.

Re: Senior engineers are living in the future

#58

Earlier quoted context omitted.

Saw a company fail because all developers were expected to master k8/helm etc. A couple of us got the hang of it well enough to get by. But almost everyone failed too. Even those of that had it working, it was a huge time sink.

In what way were the developers expected to "master" k8/helm? In the sense of actually making contributions to the k8/helm setup, or simply using an existing k8/helm setup to provide a development environment? Was there any "expert" person on the team that everyone could ask about k8, or was everyone simply supposed to pick things up on their own? (asking because my own team is currently moving in this direction, and…

Anyone who is either insecure about their own skills, or so proud of their skills in their area that they can't face being a beginner in another area, will struggle and come up with reasons not to learn it. And they'll tell their nontechnical colleagues or managers that the idea is overengineered, or they'd add more value elsewhere, until it happens or they leave.

Re: Senior engineers are living in the future

#59

Earlier quoted context omitted.

I would never fault someone for not being able to pick up a language and use it competently in 3 days. I understand why you use this as an example, with having samey syntax, but there is still nuance. I think the bigger indicator is you've been in the industry for 10 years and call yourself a PHP/Java dev. At this point you should have dabbled in probably 10-100 ways of solving problems depending on what your 9-5 loo…

Same. I've never seen anyone become proficient in a new language/platform in less than a year. Sure, you could learn Go's syntax, use it in the style of Java/PHP, and make it work, but that is not being proficient in Go and its idioms.

A year? That's a very long time for anyone who isn't a novice to learn a new language.

Re: Senior engineers are living in the future

#60
post #8

Senior means two things: - Have experience - Self learning though above experience. I met many experienced developers, but most of them failed at step 2. To me, they're still junior.

I think you can be senior without experience. To me, senior means "can handle ambiguous/incorrect/incomplete problem definitions."

This skill comes from experience. If you're talking about experience in a particular subdomain, then yes for sure.
Post reply on HN