lytefm

Yeah they bought veri.co last year and announced the integration of metabolic into their platform last week.

As the authors mention in the end, personalized nutrition based on CGM only makes less sense than also integrating sleep, stress, movement,... - which Oura is really good at.

> I think we will still need software devs, but not as many as we do today.

I'm more of an optimist in that regard. Yes, if you're looking at a very specific feature set/product that needs to be maintained/develop, you'll need less devs for that.

But we're going to see the Jevons Paradox with AI generated code, just as we've seen that in the field of web development where few people are writing raw HTML anymore.

It's going to be fun when nontechnical people who'd maybe know a bit of excel start vibe coding a large amount of software, some of which will succeed and require maintenance. This maintenance might not involve a lot of direct coding either, but a good understanding of how software actually works.

I'm not surprised. Apple ID seems completely broken to me, even when I just tried to set up a new MacBook 4 weeks ago:

Create an account via the settings page? Had to contact support because my phone number + email got stuck in some "halfway activated but can't log in" state.

Sign into the App Store + downloading some software? Got stuck in some broken form that wouldn't let me enter payment information. Had to crawl through reddit threads about how to work around this mess, just to be able to use the App Store.

I'd be fine calling myself a "AI Engineer" for having worked with TensorFlow, PyTorch and scikit-learn and having experience in running AI Models in production.

Nowadays, making requests to the API of a LLM provider is what makes an engineer a good fit for working at an AI company? Really?

Cold emailing someone who makes their contact information publicly available and might be interested in a sales pitch is not illegal in Europe. Sending SPAM is. The lines get even more blurry with automated AI tools that offer personalized sales pitches as a service.

I'd be curious how this plays out in court. Probably something like:

- If you use an AI tool to scrape leads and to generate the content but then still send out individual emails from your Mail provider, it's still a cold email.

- If you use an AI tool and also automate the email delivery, it should be considered spam.

> Does this mean that I should private my GitHub-mirror to my personal blog, because this can become a common thing? I have removed my email from my GitHub-profile now, but they can probably get it from my Git-log anyway...

It's possible to use a noreply.github.com linked to your username for making commits. And you can to change the authorship of past commits in your own repos with write access.

I try to avoid give my email in a public and processable format whenever possible.

Early this year, I've received a hostile PR for a "maintenance only" JavaScript authentication library with less than 100 stars but which is actively used by my employer.

It added a "kinda useful but not really needed" feature and removed an unrelated line of code, thereby introducing a minor security vulnerability.

My suspicion is that these low quality PRs are similar to the intentional typos in spam emails: Identify projects/ maintainers who are sloppy/ gullible enough and start getting a foot in the door.

> All of this has caused me to spiral into depression the last 1.5 years. Is it possible to get out of this situation?

Honestly, I'd doubt that working with legacy code simply causes you to feel depressed.

You might have an actual depression and changing jobs might just make things worse.

Go see some therapist, at least do some online screening for symptoms of depression.

I've had a very good time at my first job where my only task was to maintain a horrible legacy Java codebase because I wasn't depressed.

I've had some tough months in my current job at a startup, working with modern NodeJS, Python + ML, Docker stack because I was depressed.

Have you tried out working on multiple projects or tasks at the same time?

When I hit a wall, it's often futile to continue working on that single problem. So I'll just leave it as is is for a day and work on something else.

When I revisit task one the next day, I often have a fresh approach or I'm able to spot that bug I just couldn't find the previous day.

Other devs seem to prefer working very "linearly", but I'm doing better if I juggle several tasks at once.

I have the impression that some people can be software developers for 10 years or longer but they still don't "get it" while some junior devs are really great right from the start.

These Seniors might be good at duct taping, overengineering or have a "my way or the highway" mindset but aren't capable of finding and implementing a good solution given the constraints.

It probably boils down to factors like intelligence, creative problem solving, ability to focus, reading skills, knowledge retention and a healthy dose of humility.

I guess everyone can (and probably should) learn basic coding skills, but it doesn't mean everyone can become a great software engineer.

This could even play out on a broader scale and even increase the demand for software engineers.

What is going to happen if more and more people are creating lots of software that delivers value but is difficult to maintain and extend?

First it's going to be more high-level stuff, then more plumbing, more debugging and stitching together half-baked solutions than ever before.

AI might make our jobs suck more, but it's not going to replace them.

Yeah if it's more like "you work for me; I pay you as long as the results are good but will fire you at will" it's much easier to pull this off while maintaining a clear conscience.