i_think_so

(Obviously some developers are better or worse than others, so I presume your observation is assuming developer skill as a constant.)

(Yes, I know they have an onion. Try it some time. Guess which company's infrastructure blocks your anonymous request.)

That's got to be a very tricky analysis given how subjective quality is. But I'm sure there are people trying to pin it down.

Shame on whoever did that. You should lose your downvoting rights. The community deserves better.

I wish I could give you good, brief advice on how to avoid getting downvoted to death before you even get started. There are undoubtedly others who would do a better job. So I'll just say "try really hard not to appear like ChatGPT write your post."

Everything imaginable is being impacted by AI, in expected and in surprising ways. Communities are going to need to put extra effort into things that used to just happen, like welcoming new members. Here's mine.

(I hope I'm not wrong and that you're not actually a spammer. But I think my bet is safe enough. :-)

Is it possible that this article might have an agenda and is less than 100% accurate?

See my longer comment above regarding this vitamin deficiency, why shots should not be the first response, and hints at why we have this status quo.

Whoever told you that is selling something. Vitamin K is fat soluble and even the cheapest, lowest quality formulae can deliver enough of a dosage for an elephant. Unless the newborn is already bleeding, immediate supplementation is unnecessary. (Unless you're expecting to injure the newborn, in which case please get in the back of the squad car, sir, and don't bump your head.)

I suppose it's possible the newborn is already bleeding, in which case somebody should probably figure out why and address that first.

> I guess I don't see the point in rejecting the shot. It's a vitamin, it has a clear benefit, and no drawback.

Please don't give medical advice. You're not good at it.

A big whack of K (either form) in a shot can't be pulled back if it turns out to be too much for the child. If the placental diffusion just so happened to be higher for a particular child, and their levels were not so very deficient, now you've got an overdose condition to deal with.[1] Normally that's not the end of the world, but to say there's "no drawback" is just wrong. Further, it's entirely unnecessary when there are safer, titratable methods that don't involve poking a hole in the newborn, such as adding K to pumped breast milk or painting the mother's nipple. Oral dosage can be spread out over many feedings, and at the slightest indication of excess (jaundice, for example) can be discontinued without further risk.

But of course, this requires the mother to have the wherewithal to remember to do the supplementation, and modern hospital protocols are designed with the assumption that the mother is incompetent at her job. Some of us have higher opinions of women and their ability to do what women have routinely done for millennia. A cynic might also point out that the hospital can't charge you as much for a bottle of cheap gel caps as an injection.

By the way, K1 is the plant-derived form, which some of us feel is a bit better to supplement with than K2, particularly when coupled with fat intake. On the other hand, if you do intend to let the hospital shoot up your newborn instead, maybe ask to see the vial first.

[1] https://web.archive.org/web/20251206091225/https://www.vinme...

1. https://www.linkedin.com/pulse/nox-reduction-technologies-ga...

2. PDF: https://www.ifc.org/content/dam/ifc/doc/1990/handbook-nitrog...

(Except the Citrix. I never admin'ed that, only used it for a few gigs.)

I am far from being an economist or political scientist, but that's what it appears to me. Every government I can think of puts its collective thumb on the scale in the economy somehow. And I can't judge which of the metrics cited (negative productivity growth, fertility below replacement, etc) are causal and which are incidental. So I don't understand how the claim is supported by the data.

Or is the entire piece just somebody's opinion with an agenda? I'd love to hear from someone unbiased who knows better.

* Stock-based compensation not included. Void where prohibited or taxed. Your mileage may vary. Contains tree nuts, milk, soy. LSMFT.

I used to have a stack of those login cards from the Sun courses I took. (I think they gave them to us to to log in to the "attendance" system, but really they were just souvenirs to show your coworker when you got back.) They sat on my desk and were a marvelous kind of fidget device, like shuffling a very scanty deck of cards over and over.

I bought a gen 2 SunRay in the hopes that I'd get around to installing it in my LAN some day as part of my eternal To-Do list. Sadly, I trashed all of that stuff when Sun got eaten and Solaris turned into a niche tech that I was almost embarrassed to have on my resume. I wish I had that stuff now.

Thank you for submitting this link, and (if they come by here) thanks to the author for writing up such a lovely, nostalgic bit of work.

...because right now no one is hiring _anybody_ who isn't a super duper senior 100x dev. The whole world of tech is facing a generational collapse. We need to pull a rabbit out of hat soon or we're all screwed.

> Too many requests are being made, which brings down the performance of feeds for other users. Please wait a while before requesting more feed content or log in for full access

Rather silly of them to hide investor relations material behind an anonymity-hostile CDN.

PDF for those who want it. https://web.archive.org/web/20260506084407if_/https://invest...

I just want....I just want hard drive prices to come back down. *sniffle*

I wasn't trying to write a Great American [Cyber]Spy Novel. I banged out a silly short story over maybe 40 minutes while I was eating. Then I went back and cleaned up a bit of the text I didn't like and gave it to the world.

I smiled and chuckled a few times as I was writing, because that's what often happens when an author is making something he's happy with. I hoped a few others would get a chuckle out of it too. I gather that 2 people did, so far. That's good enough for me.

If you're applying to become my editor, please email me at bizinquiries@i_think_so.com during M-F so we can discuss your fee.

Comparatively very little of that "humanity" corpus is coming from Shakespeare or Swift or Douglas Adams, much as we might prefer if it did.

I am in that demographic. I have been hacking on other peoples' software as a necessity, to get it to work or to do things I wanted that it didn't yet do, all my career. LLMs came along and afforded me the opportunity to act like a full time programmer when I'm just a paranoid systems monkey who is normally obliged to treat programming as a barrier to be overcome, not a career or even primary hobby.

In my specific case, the reason I was yearning to write code but did not was simply because there weren't enough hours in the day, and I wasn't told that I should spend my on-the-clock hours doing it (unless it was for automating my job). So despite the fact that I have had hundreds of instructional hours of programming classes, learned the basics in half a dozen languages, and been "hacking" code for years, none of it stuck because I never had an employer say to me "right, you're going to be responsible for writing (or maintaining) this Perl app here..."

> Basically, I am prepared to accept that there is a friction that LLMs lubricate away, but what is the source of the friction, and why am I (and a bunch of other colleagues) not feeling that friction daily in our practice?

Learning a programming language and then not getting to use it more than a few days every 3 years means you don't actually learn the language. It's more like a pleasant evening playing a game.

You and your colleagues are, I presume, programmers. I'd wager what I just described is Greek to you. So try to imagine it this way: somebody comes out with a crazy new prototype CPU. It's got a radically different ISA, so it doesn't even have C on it yet -- you have to poke registers with a brand new language that's like Ada on mescaline and it's built on a flavor of assembly that's like nothing you've ever heard of. So your boss tells you to learn it, then 2 weeks later pulls you off the project to do something normal and takes the dev board away.

If you don't see that CPU again for 3 years, how long are you going to retain that bit of knowledge you acquired? Well, that's what it's like for us programmer-adjacent nerds who spend all our time building systems, replacing failed components, crimping cables, writing disaster recovery documents, adjusting backup schedules, and getting woken the hell up night after night because another filesystem filled up.

I have no data to share on how many of us there are out there in similar situations world-wide, but I have met numerous traditional sysadmin in my time who were competent at automating things with shell scripts, not competent at writing "software" in "real" programming languages, and are probably using LLMs now to remedy that lack of skill.

For every 10 DevOps guys there may be one trad sysadmin out there who knows enough Perl to glue the server farm together and keep it running but can't be bothered to learn Python. Or the ratio may be the opposite. But whichever it is, that demographic very much exists.

> a great idea for many domains

I completely agree. This is a great idea. If you don't do something with it I'm stealing it. ;-)