Regulations are like lines of code in a software project. They're good if well written, bad if not, and what matters more is how well they fit into the entire solution
Not sure what polish you're looking for but it's been great for me. Smart autocomplete algorithm and good chatbot that acts like a personalized Google / stack overflow. It's not good enough to vibe code full products or debug hard issues, but that's just limitations of AI.
Also it's all Microsoft, they made both the AI and the editor. I appreciate that they don't do anything extra in the editor to favor their own extensions.
The wealthy do use public schools. They pay huge amounts to live in upper class neighborhoods with wealthy peers, where a lot of tax money goes into the schooling system so the kids can take all sorts of extracurriculars and AP classes. It gets the same results as private school but the cost comes from living in that neighborhood rather than paying the school directly
It's not at a point yet where I can recommend it to non-technical people but it's getting close.
I can play almost any steam game that I can find on it, but usually need to manually enable proton-experimental. Some Unity games have weird bugs and there are some other games I still can't figure out how to run at all.
I've run into weird errors due to incompatibility between Nvidia GPUs & their drivers with my OS. Haven't encountered the issue in 4 years but having your graphics driver break means you need to fix your crazy issue with only a terminal (hope you have another computer for googling).
My dad was becoming more pro-privacy so I got him Linux Mint, and something broke that put him in GRUB and it frustrated him so he asked me to change it back.
But Linux seems to be getting better as fast as Windows is getting worse so I still recommend trying it to anyone remotely interested
Anecdotally, a friend of mine works for a state department of transportation and has been trying to get a developer and a DBA to replace some people who've recently left.
He's been having an insanely hard time finding anyone for the role, and not because of salary requirements. He's required to vet candidates through approved sources and so his department uses a recruitment firm that keeps sending him resumes from people who are substantially lying about their experience and maybe also their identity. I tried recommending someone I knew who I knew had a lot of db experience and was job searching, and he said he wouldn't be able to interview the guy because he wasn't from an approved source.
His best recent hire was a woman who understood the system well enough to create her own firm, get it govt approved, and then get herself hired as a consultant.
Bear in mind I'm just recounting what my friend told me so I may have inaccuracies in this story.
Not yet but there's a precedent for incredibly perverse incentives caused by sports gambling -- most iconically the White Sox throwing the world series in 1919.
Looking at that smalltowntruth website reminds me of someone I met in 2015.
I stayed at a guy's airbnb in Denver. He was in breach of his renting agreement by hosting the airbnb and had previously spent about a year in jail (forget for what). He said he had 2 websites that he was promoting on Facebook and were making him money. On one website he posted lots of pro-Trump content and on the other he posted lots of pro-Bernie Sanders content. This was during the primaries so these articles were largely in opposition to Ted Cruz and Hillary Clinton. He said he didn't care about either candidate but both websites were making him good money in ad revenue. He was not actually affiliated with either party.
I wouldn't be surprised if he or someone else like him had scaled up their efforts.
That was cool! Yeah this is exactly the kind of thing I'm working on too. I don't have it that you can draw like he does, but it does let you view an object in a similar way & it can stream data to a server connected over wifi so that you can see mirrored behavior on a desktop app. But it's missing so much still, you can't interact with anything yet.
Cool! Didn't know about the pen, though I've seen clips of similar tech being used.
I've got a long ways to go with this app though so it's still just a pet project. The position tracking is very suboptimal right now, so I need to switch to a better library. And then I need to start adding actual actions because right now the app is just a glorified object viewer.
I'm insanely flattered that you think it's interesting though. Very motivating to me.
I've been learning how to use Blender. For a long time I've thought that working with things in 3D could be made simpler by having an app where your phone is a sort of 3D cursor, and e.g. for modeling you could use your phone as a sculpting knife by moving it around in the air.
So I spent some time trying to make an app that allows you to do that, but can't shake the thought that such an app would work better as a Blender addon/plugin rather a standalone app. And I also am trying to figure out how people work with 3D currently, to see if such a tool would even be an improvement over existing tools.
I hate this article. It's a very smug way of blaming the dev who's just trying to make the app better when it's probably the culture that's the problem. Bad refactors usually happen because the person doing the refactor is getting a ton of pushback on it -- they probably underestimated the effort involved and are getting chewed out for taking too long on it, so they cut corners that might accidentally lose functionality, or they don't finish the desired abstraction / clean code they were going for which leaves the code less readable.
For a dev that's a new hire, refactoring the code is also a way for them to feel ownership over it. The PM should be happy that they're thinking about the way the code works and the way the code should work. It's on the company to have review & qa processes that catch problems before they lead to downtime.
I don't disagree that some of the examples given are bad refactors, but in regards to adding inconsistency I see that happen a lot more when rushing out new features or bug fixes than when refactoring; usually the refactor is the effort trying to establish some kind of consistency. And example 5 isn't a refactor it's just removing functionality. If that was the intent, the person should be told not to do that. If it's an accidental side effect of some larger refactor effort, then just add the functionality back in a new PR. Accept that mistakes happen, adopt some QA controls to catch them, and build a culture that encourages your developers to care about your product.
D) Going to be "solved" by catching someone unfortunate who seems plausible enough and lacks an alibi.