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
- What are some ways in which your company is not using the latest new hotness, but ways in which your company is doing good enough?
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.
What boring technologies/practices do you use in-house?
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.
Not gonna lie I just want to know about all the skeletons in the closet, not so much the tech stuff. I know it’s… dirty, but it’s so interesting hearing about this from other companies, and honestly pretty helpful to have other situations to compare to your own.
* What was the last original functionality you wrote that soles a real problem and does so without a framework?
* 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.
How do you see your team environment? Is it competitive or collaborative?
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.
setup a form for anyone interested in an interview https://tally.so/r/3NAPbp or to subscribe to the blog: https://powerplaybook.substack.com/
At your current role, what is your biggest challenge? What have you tried to solve it?
All I want to know is what was essential to get where they are, and what was noise.
What is an IC?
Integrated Circuit…
Internet Commentator…
…
"Do you feel fulfilled?"
- Whens the last time you used an algorithm (eg b-tree) and for what?
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.