[-] thesmokingman@programming.dev 54 points 1 month ago

I have heard the same rhetoric about IDEs, autocomplete (Intellisense, Jedi, etc.), DevOps, and frameworks. The kernel of truth across all of them is the separation between a dev and good dev. It is getting easier and easier to have something built for you using AI in your IDE in a framework that abstracts all the things away dumped into a prebuilt pipeline that deploys your artifacts for you. A dev can do that. A good dev understands the tools and knows when to dig into things.

I have yet to see a decrease in the number of good devs I meet even though IDEs slowly replaced text editors (and editors became strong enough to become IDEs). Frameworks have enabled more good devs to focus on business logic. DevOps provides solid guard rails for everything.

I don’t know if there’s an increase in the number of superficial devs. I haven’t interviewed junior dev candidates in awhile. I do know the market is flooded right now so I’d argue there might be other factors.

Also overall I do agree with the idea that letting copilot do everything for you means you don’t understand anything. Shit was the same way when cookbooks were common.

[-] thesmokingman@programming.dev 72 points 2 months ago

This is a common problem. Same thing happens with AWS outages too. Business people get to manually flip the switches here. It’s completely divorced from proper monitoring. An internal alert triggers, engineers start looking at it, and only when someone approves publishing the outage does it actually appear on the status page. Outages for places like GitHub and AWS are tied to SLAs that are tied to payouts or discounts for huge customers so there’s an immense incentive to not declare an outage even though everything is on fire. I have yelled at AWS, GitHub, Azure, and a few smaller vendors for this exact bullshit. One time we had a Textract outage for over six hours before AWS finally decided to declare one. We were fucking screaming at our TAM by the end because no one in our collective networks could use it but they refused to declare an outage.

[-] thesmokingman@programming.dev 48 points 3 months ago

The problem is the underlying API. parseInt(“550e8400-e29b-41d4-a716-446655440000”, 10) (this is a UUID) returns 550. If you’re expecting that input to not parse as a number, then JavaScript fails you. To some degree there is a need for things to provide common standards. If your team all understands how parseInt works and agrees that those strings should be numbers and continues to design for that, you’re golden.

[-] thesmokingman@programming.dev 50 points 4 months ago

What? A good chunk of hackers are left-wing and go after authoritarian or repressive targets. I have no idea what you’re referring to unless you’re talking about the recent Korean ISP story which is so far off from your categorization.

The other option is Poe’s Law.

[-] thesmokingman@programming.dev 46 points 4 months ago

I’d argue it was taken from us several years ago when Raspberry made the decision to prioritize business customers over education and hobby during the chip shortages.

[-] thesmokingman@programming.dev 52 points 5 months ago

It’s P2W. There’s absolutely no way their grind example is actually achievable by a casual player.

[-] thesmokingman@programming.dev 65 points 8 months ago

That’s how little they got‽ Holy shit. That’s the steal of the fucking century for all that content. Reddit clearly puts the same stock in its negotiators as it does its 3rd party ecosystem. Anyone who values them more than maybe 2x this price for their IPO is a fucking idiot. Forget Trump’s Art of the Deal. spez needs to write a book.

[-] thesmokingman@programming.dev 56 points 9 months ago

Whether or not you think he should be jailed for leaking CIA secrets, the dude had child porn. He deserved a serious sentence because he expressed zero remorse for that. Along those lines he couldn’t even fucking pretend to have leaked the state secrets for any other reason than the CIA was a shitty place to work. You gotta play the fucking game if you’re gonna fuck with the government. You can’t just be a crusty old coder.

[-] thesmokingman@programming.dev 52 points 10 months ago

I’ve found that many people can’t differentiate “swearing around” vs “swearing at.” If I am swearing, it is to add filler words to my sentences that serve many purposes. I am not (rather, very rarely) attempting to insult or denigrate someone else. I do not understand why someone takes offense at “I really struggled to hit my fucking steps today” or “Shit I dropped the fucking ball.” I do understand why someone takes offense at “you ignorant fucking walnut” or “fuck you you fuck trumpet.” Conflating the two situations is so fucking dumb.

[-] thesmokingman@programming.dev 48 points 11 months ago

The biggest reason not to use a single account like this is that you lose everything if you lose the owning account. It’s bad advice to say you should absolutely do one or the other. It’s good advice to consider the risks.

[-] thesmokingman@programming.dev 51 points 11 months ago

Context for anyone also confused

[-] thesmokingman@programming.dev 59 points 1 year ago

This is more a Chromium vulnerability than a GPU vulnerability. Firefox and Safari aren’t vulnerable.

view more: ‹ prev next ›

thesmokingman

joined 1 year ago