I've had no problems following the advice of my weight loss program and r/Zepbound etc.
I've had no problems following the advice of my weight loss program and r/Zepbound etc.
One place I worked decided that it'd be easier to build an AMI and provision quasi-ephemeral EC2 instances to developers instead of putting the time in to pare down the landfill of dev dependencies they had. This whole process was, of course, orchestrated by a custom CLI that would itself randomly break in odd ways.
Fun times.
I feel like this is a real barrier to getting effective contributions from outside of existing team members. Some colleagues seem to see this as an advantage.
Take a tool like Gradle. Bigger pain in the ass using an actual cactus as a desk chair. It has a staggering rate of syntax and feature churn with every version upgrade, sprawling documentation that is clearly written by space aliens, every problem is completely ungoogleable as every single release does things differently and no advice stays valid for more than 25 minutes.
It's a comically torturous DevEx. You can literally spend days trying to get your code to compile again, and not a second of that time will be put toward anything productive. Sheer frustration. Just tears. Mad laughter. Rocking back and forth.
"Hey Claude, I've upgraded to this week's Gradle and now I'm getting this error I wasn't getting with last week's version, what could be going wrong?" makes all that go away in 10 minutes.
Is that remotely plausible? I can't imaging faking a scan being easier than just walking down the hall to the copier room.
This niche position has had some interesting ramifications for them and for me. They clearly incur a lot of technical debt once their business relies on bespoke software. On the other hand, they own the software and can get an immediate response or new feature or upgrade from me, limited only by my time. And in the end, this ends up saving them time and money. It gives me a permanent and unending flow of work. But if I die, they're pretty screwed.
One reason I don't vibe code things even now, even simple components that could easily be vibe coded, is that I remember and know where everything is, every function or line of code that might be causing issues, because I wrote it myself. I know right away where to look for a query that might be throwing errors after a database upgrade, for instance.
As a manager I assume you would probably not want to go down the road of hiring someone like that, but for companies of a certain size it's an acceptable compromise. However, I wouldn't want to hire someone like that myself unless they were extremely reliable and didn't rely on AI to write any of their code.
https://i.pinimg.com/736x/0a/e5/36/0ae536826bb1cf643e6f05066...
I'm not too sure what you're referring to with a "write off day". I am on the highest dose currently and don't have this issue. I maybe get some sleepiness the day after taking it but I can still do things. However that effect has also subsided a lot after taking it for long over.
Every medication will have pros and cons. I'm having huge success on the medication and the slight issues I have are a worthy tradeoff personally.
Some people aren't comfortable leaving the house when their rear is flowing like Niagara Falls.