...
Proceeds to use Svelte cuz it has the exact features I want
React is popular but I honestly don't care about llm weenie vibe coder junior devs being biased towards react. Lions don't concern themselves with the opinions of sheep.
The majority of shit apps are being made with react sure.
But skilled seniors who intend to make something robust don't even tend to have an llm enabled that will even influence their opinion on the first place. The majority of senior devs keep repeating the same sentiment: llms primarily are slowing them down more than helping.
Junior devs that crutch on llms are falling behind and the quality of their output shows. They grow slower and produce worse output.
It's one thing to use it for monotonous tasks, but if it influences your higher level important decisions you are probably already cooked.
Whenever a racing game comes out and they put sonic in a vehicle, I wish they'd note it in the lore itself
It's gotta be a case of "sonic we are putting you in this car to make this race fair" which I'd find hilarious if they acknowledge it out loud.
IE have him say something like "don't make me get out of this car" or whatever as a threat, or, "I'd have won if I wasn't in this hunk of junk" or etc
The entire concept of Sonic in a car is hilarious to me, because while everyone else is going fast, he's just like "oh my goooood why is this thing so slooooww"
this facility has never had this issue until the FBI showed up to commandeer their incinerator.
Says who?
For all we know they've had issues everytime they incinerate but they ignored it cuz a lil bit of smoke from 1 cat is way easier to shrug off compared to a huge amount of meth
It's very possible they just have been ignoring the problem because normal smoke from incineration a very small cadaver isn't a big deal, whereas meth fumes are extremely toxic and not something you can just shrug off
Lord knows I've worked with workers who have the "I've been doing it this way for 10 years and never had an issue, don't be a pussy" type of attitude too
So hard to say, without more info it's basically just us speculating.
The article has not stated who was responsible for operation of the facility.
It's more likely the responsibility was on the staff to ensure the equipment at their own facility was functioning right
This sort of error should have been covered by prior operation licensing checks, a facility with an incinerator on premises shouldn't have negative pressure issues
So something somehow caused a negative pressure issue.
Usually the culprit is some kind of exhaust fan being run, or a door being left open too long
Based on time of year and how hot out it is, I wonder if a staff member left a door propped open or something.
Incinerator systems need positive pressure overall.
Anyone who lives in the north and has a gas based furnace heating system knows how deadly negative air pressure can be...
The incinerator is usually used by animal control officers to dispose of euthanised animals, but local authorities said it can also be used by law enforcement to burn seized narcotics.
The incident was caused when smoke was pushed in the wrong direction because of negative pressure, according to Assistant City Administrator Kevin Iffland.
That sounds like it wasn't a method specific issue, and if anything had been burnt in that incinerator it would've caused the same issue.
Sounds like the facility wasn't setup right, any facility with an incinerator should definitely have positive pressure, not negative.
Getting a later special meeting request with the ceo, at one company, because he wanted feedback on their interview process itself. He then offered me a different job and I had to decline cuz I already accepted another (this was a few weeks after the initial decline I gave)
In another case they just fast tracked me and I ended up declining the job anyways (didn't like the job)
I'm full time employed but I still do occasiobal interviews to keep feelers out for how the market is. But I typically decline most offers cuz they're not good enough to get me to actively quit my current job.
In the "right" use case, story points should just represent relative effort.
The hours dont matter, its more about ranking how challenging a task is, in order to help the manager rank the priority of tasks.
You should have typically 2~3 metrics:
Points, which represent relative effort of the task to the other tasks you are also ranking.
Value, how much value does doing this task provide, how important is it
Risk, how risky is it that this might break shit though if you make these changes (IE new features typically are low risk since they just add stuff, but if you have to modify old stuff now your risk goes up)
If you have a good integration testing system automated, Risk can be mostly removed since you can just rely on your testing framework to catch if something is gonna explode.
Then your manager can use a formula with these values to basically rank a priority order for every ticket you now scored, in order to assess what the next thing is that is best to focus on.
Passes their traffic through literally the other side of the world
Speed plummets
ShockedPikachuFace.jpeg