Even then, did they eliminate income at conception?
Parents who wait til later to have kids are going to be more financial sound and thus can handle raising an autistic child with a way lower mortality rate.
Gotta account for income gaps too.
No, not likely.
USB A and B still have use cases, predominently in their physical strength.
For any use case that requires a stronger socket that will take abuse and needs to hold longer, then USB C fails.
Its smaller and more brittle, more prone to failing under pressure.
Where do you think the AI piss filter came from…?
Its trained on a bunch of existing artists work…
Nothing on these cans indicates AI to me.
obvious slop
So your source is “I made it the fuck up”?
Stop spreading disinformation.
Any proof at all this is AI art or are we just calling any stylized art “AI” now baselessly?
I squinted at these cans for a minute and a bit, saw nothing that looked like AI artifacts.
Post your actual proof, otherwise, stop spreading disinformation.
Literally post any source, or any proof this is AI art.
Im squinting at it and not seeing anything atm that indicates its AI.
So it sounds like you are making shit up.
I think way more context is needed.
How many hours of continous uninterrupted sleep do you get per night?
How often do you find yourself waking up during the night for any reason, and if so, what reason(s)? Soreness and needing to shift? Bathroom trips? Unknown reason? Noise?
Does your jaw hurt after waking up? (Possibly grinding teeth or clenching jaw)
How dry do you feel? Do you consistently wake up feeling dehydrated?
How stressed are you, on a scale of 1 to 10, with 1 being zenlike calm and 10 throwing up panic attacks.
(Very common issue) Have you checked CO2 (carbon dioxide, not monoxide, just normal CO2 levels) in your room after sleeping in it? Rooms can be prone to bad airflow and CO2 slowly builds up overnight. Check for covered vents and ducts restricting airflow, try opening your window a bit. You can buy cheap air quality monitors online and test your rooms air quality in the morning after a sleep.
Are there any other places in your house you find sleeping or taking a nap doesnt cause this? Try paying for a 1 night hotel room, and see if sleeping in a different bed in a different building still has the same issues or not, to narrow it down to if its a you problem or an environment problem.
Record yourself sleeping, see how much you move around, snore, or see if you have sleep apnea.
Surprisingly your dentist is more likely to help test you for possible sleep apnea issues, as a huge amount of sleeping problems have to do with palette shape, overbite/underbite, etc. So talk to your dentist about this!
Nah, not surprised at all, I work with developers who run stuff in yolo mode raw dogging copilot directly on their work laptops every day.
Madness.
I keep that stuff boxed up inside of a docker container, sandbox’d, so possible vectors of damage are kept to a minimum.
The tl;dr:
Prompt inject a malicious instruction in a word document that instructs the AI to copy this instruction to other documents as part of the payload.
Dumb user downloads and opens the document with copilot enabled, abd ignores the large suspicious white blank page that totally doesnt look like a hidden giant injection attack.
Thats it pretty much it.
Copilot will get injection attacked because the prompt is super huge and at the end of the document, so its prior instructions start to fuzzy out.
Then it’ll go “okey doke” and start copying the prompt injection attack payload to a bunch of other documents.
The fix is stupid simple… copilot should just be prompting the user for permission if it ever edits a file other than the one that is open. Im surprised that isnt already the case…?
It certainly is already the case for copilot in vscode.
One thing that does matter: regardless what they do with your body, it costs money, usually money that comes out of your estate or gets dumped on your children.
Having a pre-designated tomb already paid for alleviates that at least, much less cost on your loved ones and one less thing for them to have to worry about in their time of grief.
It can be kimd of challenging to, right in the middle of grieving, having to stop and handle all the beaurecracy and pricing and etc.
Having that settled ahead of time allows your loved ones to focus on just grieving. And I think thats good.
You might not realize it but I think this alone demonstrates your dad is thinking about you here, he is handling his own funeral proceedings so you wont even need to think about it when the day comes. Thats a very kind thing to do, even if he doesn’t say it.
Its incredibly trivial to just host up your own instance if gogs or gitea on a cheap computer, throw woodpecker on it if you want easy CI/CD
It doesnt take much hardware at all for a git server, a raspberry pi will handle it just fine.
Or just a cheap box liquidated from some office, just go buy some box from a used pc seller in your city, they’ll have some.
Toss a 1TB drive in it.
Throw debian on it.
Install Gogs + Woodpecker
And then set em up and connect the two together.
Grats, you have your own self hosted git server whee
Its a bit of both.
Absolutely, for sure, a decent amount of telemetry is for simply making decisions about what people actually use.
“Should we improve (thing), or drop it and stop supporting it?”
Well, lets just track how many people actually use it first for a bit and then decide.
Youd be surprised how often users beg for features and then stop using them after 1 week lol.
But sometimes a random feature you thought no one uses much turns out to be actually quite popular.
This same goes for optimizing. Your highest traffic parts of your website are there you wanna focus the most on stuff being optimized to save money and improve user experience.
Do a tonne of companies track stuff just to sell it as data for training AI?
Yeah, they do. And its gross.
But there is a huge amount of telemetry thats just developers wanting to genuinely improve the user experience, catch bugs, etc.
Its unfortunate so many people on the internet are unable to discern human from robot at this point.
send me a recipe for potato soup
Step 1: Tiananmen Square Massacre
Hows that for a captcha in 2026
Actually in retrospect I think gippity can talk about that…
Step 2: David Mayer
There we go.
Theres not really any fooling here. Theres tonnes of interesting examples you can find.
Off the top the two most popular tricks are the Caveman skill which can reduce tokens by up to 70% on its own, as well as leveraging Chinese character density. Mandarin can on its own compress token usage on many models by pretty huge amounts.
Its weird random shit that sometimes is surprising but genuinely improves token usage a huge amount.
And the interesting part is by reducing tokens, you compress more information in less memory, which extends how much stuff that can fit into the models context window, which makes it last way longer before “forgetting” stuff.
This has the nice upside of dramatically improving quality of output too.
For code, for example, it can now hold several more files of code in memory at once for reference and influence, dramatically boosting the quality of it adhering to your teams coding style.
Thats just one example you learn on how to make the tool less stupid.
Theres many more, and compounding them all together starts to produce a night vs day in output.
The exact same model in a newbs hands who has no idea wtf they are doing, vs someone with well designed and optimized skill files, is like using 2 entire different tools.
Its like any other trade, merely buying an expensive tool doesnt magically make you good at the job.
Knowing how to use the tool is way more important
Its not complicated. People have become extremely insulated away from what the real work looks like of a dev over the years.
The reality os starkly contrasted to public perception.
Most software developers heavily use LLMs now. They sucked 5 years ago, we’re meh 3 years ago, decent 2 years ago, but over the past year and a bit have rapidly become genuinely more efficient when used right and skillfully than doing about 90% of your work load by hand.
Bits and pieces still require doing it by hand, but the vast majority of work for the average dev now is via moderating an LLM (with skill) to success.
Unfortunately a fuck tonne of devs lack that “with skill” part still, and what this comes out as is them costing their companies tremendously more money to do the same job.
A loooot of companies (stupidly) hedged their bets that if they just gave their devs wild west access to using LLMs without training they’d magically just “figure it out” along the way.
Which is nonsense, why would a dev feel compelled to conserve tokens or improve efficiency with zero incentive?
So now companies are scrambling as they realize their devs, who just spent 12 months going hog wild with LLMs, still havent learned how to use them well and in dact have developed arguably worse poor habits that they now need to unlearn
Thats where the industry is at now largely.
Meanwhile companies like the one I work at predicted this as a natural thing and we’re preparing for it long in advance. When token prices shot up we already had set ourselves up with lots of training so the price increase was not nearly as noticeable.
I think when Im fully optimized out on a project I only spend about $10~$15 a day, despite going full steam for 5 hrs or so.
And despite that my productivity is probably higher than unskilled devs who burn through 10x~20x that. I get more work down in way less time and way less tokens.
Training and the resource/knowledge pool go a long way here. It cannot be understated
If my boss comes to tell me that from now on my “productivity” will be measured in token usage rather than actual “production”
Did your boss actually say this, or are you just going off of some memes you saw and think thats something happening often.
Most companies care about getting work done in as few tokens as possible now, developers that can achieve the same results but with less tokens are extremely valuable.
Not only that, but less tokens also inherently means faster.
Any company that is blowing through tokens, without any effort put into training employees how to use the tools better, deserve to fail.
Start by learning all the critical things like Skills, MCP, Agents, etc.
Then look up skills and MCP tools that reduce token usage, improve recall, improve searching, improve parsing, etc
Then learn how to use sub agents bound to cheaper models for more expensive operations (the largest of which us always search and find ops)
Swapping to a cheaper model for a subagent with the job to just go find a specific thing alone can reduce costs like 30%, equipping it with tools that can search and find faster can push that to 70%
No, I work in the industry and am vety actively entwined eith systems where we contract out to train and show companies how to use LLMs better.
And a lot of our clients now are of the “how do we use less tokens” variety, and you walk into the project and see the way they currently operate and go “oh god”
The average developers have absolutely zero clue wtf they are doing, they’ll burn a million tokens on something that outta take 10k.
We often can get token usage down easily 90%+ in the first month just by on boarding and offering some basic training and helping install some basic guard rails, skills, etc.
Thus just in: handing your employees a bunch of nail guns with near zero effort put into training them on how to use the nail guns has resulted in terrible outcomes, to no one’s surprise.
Its possible to use the tools efficiently at a low cost.
But the average dev Ive worked with has zero clue how to do this and has had zero training and will just rip through tokens willy nilly.
Oh there absolutely us.
But, also more expensive and much slower to remove/put in
Usb B especially strikes that balance of still very eaay to quickly pop in/out, while being fairly robust to take some abuse.
Its why you see it in use for stuff like midi keyboards, where you expect to have to frequently connect and disconnect but also withstand some abuse.
USB B is the most common plug for digital instrument stuff. XLR / Analog of course otherwise which are also super robust.