11–20 of 26 posts
I couldn’t help slipping into reading this in the voice of David Attenborough. “If you look in under the jungle canopy you just might catch a glimpse of the elusive product engineer. Festooned with their hoodie and mechanical keyboard. What a rare and magnificent find!“
PE in many US states means Professional Engineer, and if you use it in the wrong place, state licensing boards will come after you.
Now I might be out of the loop, but this -is- a software engineer if they're doing it right, right?
So, the author suggests to look out for a specific trait in programmers. To care about the essence of what they actually work on. I agree but why the need for the terminology
Now I might be out of the loop, but this -is- a software engineer if they're doing it right, right?
> if (text.trim().length() And then they released the product in Japan and got complaints that there were a whole lot of special requests that were being ignored (because you can encode far more information in those two characters) Maybe you do need a software engineer after all?
Interestingly, while interviewing this has always been my bane, as the typical interviewing process goes along the tech stack and tech-related trivia (probably because it is easier to assess), and almost never towards the product side of things.
And with the tech stack questions those are always in favour who are interested in the latest version of framework X, as opposed to real world problem solving. And don't even mention leetcode :)
> if (text.trim().length() And then they released the product in Japan and got complaints that there were a whole lot of special requests that were being ignored (because you can encode far more information in those two characters) Maybe you do need a software engineer after all?
The fact that one type of complaints get converted into another type is an unforeseen consequence. But shipping the change is still worthwhile because it's the only way to expand your domain knowledge and learn about those consequences.