That depends on how quick the feedback loop is for your decisions. If it takes weeks or months to find the impact of your changes, or worse, if you're insulated somehow from those changes, you may not be pushed toward improving the quality of your code.

Lolololol, sorry, I can't help but laugh a bit because some of the most entrenched companies are also the slowest moving.

> So I don't really see the need for the blatant lying.

Because this is an advert

It depends, which is really funny.

My brain on a Monday in a crap mood driving on the highway: that jerk that just cut me off has ruined my entire day.

My brain on Friday after good sleep and a relaxing morning: heh look at the guy, he's definitely in a hurry. Hope he gets where he's going, back to my jams!

I try to train myself to remember to be Friday brain, but sometimes Monday brain comes out and I'm in a funk that makes me forget I actually have a choice about NOT reacting a specific way. I like to think I'm getting better at consistently not sweating the small stuff and just letting those instances go without giving them an appreciable amount of mental space better suited to relaxing and listening to good music.

Best digging I ever did was in a torrential downpour for 4 hours. Mud and grass was flying everywhere, my shoes were squeaking as they drove down the shovel. I was soaked to the bone and my heavy, cotton clothes slapped freely against my skin with each shovel full I tossed to the side. That was some of my favorite digging ever.

I'm concerned for a future where adults stop realizing they themselves sound like LLMs because the majority of their interaction/reading is output from LLMs. Decades of corporations being the ones molding the very language we use is going to have an interesting effect.

Oral has felt very effective for me. I take a daily supplement that has roughly 100% of the recommended daily dose of everything. I split it in half.

For D3, it is 25mcg / 1000 IU / 125%

After splitting in half it's 12.5 mcg / 500 IU / 62.5%.

I take with some fat-containing food to allow ir to absorb which is usually breakfast (yogurt, some nuts, some kind of fruit, oats), and it's a night and day difference in my mood (how easily I can control my temper if already agitated, how easily I brush off annoying stuff, takes the intensity off of my reactions and mood during conversations).

I did a blood test before starting, and if normal is between 30 - 70, I was at 10. Dr prescribed megadose of D2, followed by daily D3, but I skipped on the megadose and went straight to D3 -- makes me wonder if a megadose would build up my stores since D is fat-soluble and make it so I could miss a day and not notice.

All of the above is anecdotal from me, a self-professed cave dweller, but it's been a couple of years now, and I still notice the difference. Also, what I heard from people in Boston is that 90% of them are on a vitamin D supplement. My friend from there laughed at me when I was raving about it, saying "yeah, literally everyone here is on it".

Follow up to this: I did my latest blood test after a couple of years and I'm now hovering at exactly 30. I should probably take that other half.. but my Cobalamin is at the high end so may swap to pure vitamin D instead

Extending this -- unlike real slot machines, there is no definite state of won or not for the person prompting, only if they've been convinced they've won, and that comes down to how much you're willing to verify the code it has provided, or better, fully test it (which no one wants to do), versus the reality where they do a little light testing and say it's good enough and move on.

Recently fixed a problem over a few days, and found that it was duplicated though differently enough that I asked my coworker to try fixing it with an LLM (he was the originator of the duplicated code, and I didn't want to mess up what was mostly functioning code). Using an LLM, he seemingly did in 1 hour what took me maybe a day or two of tinkering and fixing. After we hop off the call, I do a code read to make sure I understand it fully, and immediately see an issue and test it further only to find out.. it did not in fact fix it, and suffered from the same problems, but it convincingly LOOKED like it fixed it. He was ecstatic at the time-saved while presenting it, and afterwards, alone, all I could think about was how our business users were going to be really unhappy being gaslit into thinking it was fixed because literally every tester I've ever met would definitely have missed it without understanding the code.

People are overjoyed with good enough, and I'm starting to think maybe I'm the problem when it comes to progress? It just gives me Big Short vibes -- why am I drawing attention to this obvious issue in quality, I'm just the guy in the casino screaming "does no one else see the obvious problem with shipping this?" And then I start to understand, yes I am the problem: people have been selling eachother dog water product for millenia because at the end of the day, Edison is the person people remember, not the guy who came after that made it near perfect or hammered out all the issues. Good enough takes its place in history, not perfection. The trick others have found out is they just need to get to the point that they've secured the money and have time to get away before the customer realizes the world of hurt they've paid for.

I'd do the same thing I'd do with anyone that has a different opinion than me: try my best to have an honest and open discussion with them to understand their point of view and get to the heart of why they believe said thing, without forcefully tearing apart their beliefs. A core part of that process is avoiding saying anything that could cause them to feel shame for believing something that I don't, even if I truly believe they are wrong, and just doing what I can to earnestly hear them out. The optional thing afterwards, if they seem open to it, is express my own beliefs in a way that's palatable and easily understood. Basically explain it in a language they understand, and in a way that we can think about and understand and discuss together, not taking offense to any attempts at questioning or poking holes in my beliefs because that is the discovery process imo for trying something new.

Online is a little trickier because you don't know if they're a dog. Well, now a days it's even harder, because they could also not have a fully developed frontal lobe, or worse, they could be a bot, troll, or both.

I found it highly complex, but chalked it up to my own unfamiliarity with both C and the rust language and what they are trying to accomplish.

I found C way more approachable and rust filled to the brim with more rabbit holes and "logical-in-their-own-world/reality" way.. but again, I believe that's due to my own inexperience. Truthfully, in 10 years when rust fervor has died down and it has become more normal, I could see people vomitting at the thought that rust was pushed into the kernel, and there to be a strong push for not removing it but rather simplifying the code somehow? I'll definitely be writing another handful of projects in rust again in the next couple of years though, I liked how my last ones ended up