HNHacker News
TopNewBestAskShowJobs

dnoberon

189 karma · joined August 10, 2017

submissionscomments
dnoberon··on Lua 5.4.0 beta
Do you have an example use case you could share?
dnoberon··on Ask HN: What do you expect from a senior software engineer?
There's another comment that makes the same observation about the senior title on the resume. It's almost like the first thing you have to figure out when talking to a senior engineer is: title or talent? (I know talent might not be the best word, but it sounded neat. I also think talent doesn't refer to an inherent ability to do something but a set of skills developed over time to a high degree of efficiency)
dnoberon··on Ask HN: What do you expect from a senior software engineer?
"Unfortunately in 2019, the title of being 'senior' can be given to literally anyone (even with less than 2 years of experience) in their own organization but elsewhere, they are equivalent to a entry-level coder with a heavily decorated CV."

This situation is one of the reasons I asked the question. The title is being overused imo - and assigned by management to developers instead of by peers or an actual technical benchmark.

"So my approach is more or less of a senior-software-engineering CAPTCHA test."

I love this quote, and will use it from now on :D

Personally I think the industry as a whole is fairly bad at judging a developer's skill level at anything past a junior level when it comes to hiring.

dnoberon··on Ask HN: What do you expect from a senior software engineer?
I think that also highlights that they should care about the big picture enough to even worry about breaking existing things - that and be able to see the big picture at all.
dnoberon··on Tell HN: My best productivity hack
My office is an addon, taking the place of some cubicles. The offices are frigid and I've often wondered if the ventilation wasn't corrected for the new layout.

I'm going to pick up a monitor and see what I run in to. Easy fix for now is to get up and walk :P

dnoberon··on Why waste time?
The post was pretty self-deprecating for sure. I didn't even think about the opinions of other people, or customers, in building a tool. A hiccup in a tool or library that I can live with or understand, might not be acceptable to another party. Thanks :)
dnoberon··on Why waste time?
I loved that article. Thanks for your response - I did like the bit about customization a lot. It makes special sense in a work environment in which you might not want to introduce a third party dependency I guess
dnoberon··on Why waste time?
Excellent point. I was talking about this to a friend of mine - he has a coworker who calls this type of thing "developer traps". Talked about using the tool and moving on, eventually finding something that someone hasn't done or that you do feel you can do better
← PreviousPage 2 of 2