Will have an opening on my team shortly for a Product manager 2 role. We are a dev first, fast moving, technical (coding) team building great things like terminal, WSL, powertoys, sudo, edit, windows advanced settings and much much more. Ping me if you think you’ll be a good fit.
You wanna fix the budget? Start with the biggest freeloaders of all—churches. Tax ‘em so hard even the collection plate gets audited. If your pastor’s rockin’ Gucci while preaching humility, it’s time Uncle Sam gets a cut.
I’ll gladly vote to tax religion. All of ‘em. Y’all out here tithing like it’s 1400 B.C. while preaching against education—how do you think we ended up with a country full of folks who think science is witchcraft and the earth is 6,000 years old?
But sure, let’s cut education instead of asking the megachurch down the street to pay a dime. Real galaxy brain stuff.
H-1B DATA MEGA-THREAD 🧵
I downloaded five years of H-1B data from the US DOL website (4M+ records) and spent the day crunching data.
I went into this with an open mind, but, to be honest, I'm now *extremely* skeptical of how this program works.
Here's what I found 👇
#ForbesUnder30 lister Spencer Hewett’s retail technology company Radar is gearing up for the busy holiday season. The startup, which creates sensors that are installed on store ceilings to monitor where any item is at a given time. https://t.co/W6crNYZL7i https://t.co/W6crNYZL7i
@ayuninotayutu I was the same. I used to love to go to book stores and just read programming books to try to learn. I found I learn best by learning ideas, from books or presentations, then building something myself.
@PeteOlusoga I was one told. Learn if you are a starter or finisher. Teams need both and most people fall into one of the categories. Curious if you’re a starter and if there is a term for this.
Here’s the thing folks. I’ve been coding 32 years. When something like this happens it’s an organizational failure. Yes, some human wrote a bad line. Someone can “git blame” and point to a human and it’s awful. But it’s the testing, the Cl/CD, the A/B testing, the metered rollouts, an oh shit button to roll it back, the code coverage, the static analysis tools, the code reviews, the organizational health, and on and on. It’s always one line of code but it’s NEVER one person. Implying inclusion policies caused a bug is simplistic, reductive, and racist. Engineering is a team sport. Inclusion makes for good teams. Good engineering practices makes for good software. Engineering practices failed to find a bug multiple times, regardless of the seniority of the human who checked that code in. Solving the larger system thinking SDLC matters more than the null pointer check. This isn’t a “git gud C++ is hard” issue and it damn well isn’t an DEI one.
@ayuninotayutu@sreekeshiyer Agree. The barrier to entry with Python is very low. It made it a great language for experimenting, for non-programmers. As the community grew so did the tools, then things like Numba were created which ultimately runs CUDA on the GPU.