>Buy all your engineers an arduino kit with sensors and blinkylights and motors.
I would love this.
I mean, it's basically what my job is (write code to make hw do blinky stuff - gross simplification, but yeah...) anyway, but I would find getting that to be really cool. Of course, my SO would just see it as yet more HW taking up residence here (I'm remote and my company sends me all sorts of HW that I need).
> "As the company grew, the founders wanted everyone to experience different parts of the product so we could get closer to all our audiences and understand how the product works," a DoorDash spokesperson said
Does that mean delivery persons get to be an engineer or a CEO for a day?
Or it might just be some nerdy tech that a very small percent of people in the tech community feel the need to try and convince others that it is the future. It is not.
And no, seeing clearly is not a value. It is a necessity.
No. I'm not going to put one of those on my fucking head just to use a computer. I'm NOT. I already dislike wearing glasses (and contacts, etc).
To think people are going to do this in mass, it's just stupid thinking.
Edit: Okay drive-by downvoter(s), I get it, The above didn't "add" anything to the discussion. But you know what, this has been discussed and THE MASSES AREN'T GOING TO WEAR THAT SHIT.
Yeah, you have the average programmer who spends so much time worrying about what FE framework to use, then you have the programmers at the level of the two you mention who just put out so many working projects. All the cargo culting most devs do is just waste.
> Nobody is making $300k as a junior engineer. And certainly not getting promoted to senior engineer within a year on top of that. Stop talking out of your ass.
>>Well I do know someone who pulls that as a junior but he also has a PhD in inverse kinematics simulation and that job was really needed.
This is the problem with using words like nobody, always, etc. Someone will usually (see what I did there?) come along with one single piece of anecdata and think the original statement is invalid.
>Yup. This looks awful — and is error prone and slow and probably wins some kind of award for being unPythonic — but it works. And I wrote it and I can read it. We can improve tomorrow.
That's the key takeaway. Write it once to get it working and understand how to solve the problem, then write it better.
"Hence plan to throw one away; you will, anyhow." - Fred Brooks