Ask HN: If you could ask an IC from another company anything what would you ask?
alot of the products and features we use everyday are built by faceless software engineers who arent in the limelight. I thought it might be interesting to start a blog where each week I ask an software engineers/ics(individual contributors) from a different company a few questions to learn how they do things differently.
questions I'm thinking could be interesting: - Whens the last time you used an algorithm (eg b-tree) and for what? - What did you set on fire and what happened next? - whats a new interesting tool or site youve been using lately? - What feature did you build youre proud of and why?
How does that sound? What other questions would be interesting to hear? and is anyone interested in joining to be an interviewee
27 comments
[ 4.9 ms ] story [ 70.9 ms ] threadIntegrated Circuit…
Internet Commentator…
…
What I'm getting at with this one is we see a lot of talk about whatever the latest tech fad is, but I'd be interested in knowing areas where the old way of doing things is working well enough to not change.
The idea is to find out if management is spending time stack ranking/comparing individuals or are they spending their time on the mission and enabling engineers to succeed in that mission.
Dysfunctional, disorganized, toxic, and downright incompetent.
I'd be curious to hear how many people like me would answer "for a coding interview" for this question.
I haven't coded such an "algorithm" since 2002 or so. The closest I've come is calling some framework library's binary sort method.
The times in recent years where I have used such things have tended to be technically successful and commercially worthless, while the things that paid off had a tendency to be churning through piles of tedious and stupid.
Also a great question. As a manager, my first question would be to ask why a library wasn't used for algorithm X.
In grad school, I wrote a complete implementation of Rijndael encryption for a crypto class, but I would never expect (or want) anyone to try to build that themselves for production software.
People tend to hire others to do the stupid and tedious stuff. Hence most jobs are stupid or tedious. I know mine is.
Usually, what companies want is people that can handle db failovers, deploy k8s services, know how to talk to business, and write good enough code. It’s sad, but it is what it is.
Part of me wants to try harder to find something better, but every attempt I make is crushed by my never ending lack of motivation/willpower. Another part of me wants to just get out of programming completely since the reasons I became a programmer are dead or were perhaps a fantasy all along.
I'm a boring tech evangelist. I like foundational, long-lasting knowledge, the more foundational the better, even if it's harder to acquire initially, to the extent that my degree is in EE instead of CS for much the same reason an aspiring writer might major in Classics instead of English. Tell me about your dull uses of C, of Debian, of Bash, of PHP, of PostgreSQL. And then tell me about your slightly shameful uses of Perl, Jenkins, etc. We focus so often on what is new and shiny and promises the world - but we already have a world to appreciate, and it's right under our feet.
* How did you provide test automation coverage for that original code you wrote?
Those two questions are enough to peer deeply into any software team. I wish this weren’t true, because these questions are incredibly shallow, but that’s g to he state of software employment.