We work on a GoLang productivity extension for Visual Studio Code (https://www.tooltitude.com/). We are growing, but not as fast as we wish we did.

Our self hosted workers don't work. My understanding is that the control center is on the github side.

You actually could do a lot of stuff in VS Code. See rust-analyzer or our extension: https://marketplace.visualstudio.com/items?itemName=tooltitu...

I think it's not even downturn. I would call it rebalancing.

For me it's iPad Air.

There are still a lot of SWE jobs which aren't filled. They just don't pay as well as the many eliminated jobs from the news.

But, they often still pay far better than just about any other career you can do.

I'm a fairly unremarkable developer who works for a no-name tech company, but still make twice as much as my friends my age who are in law or accounting, even finance.

Only ones who even come close are in non-white collar jobs with unions and access to lots of overtime hours that they pick up. Their base pay isn't even close.

>But, they often still pay far better than just about any other career you can do.

Yep, that's completely true.

>I'm a fairly unremarkable developer who works for a no-name tech company, but still make twice as much as my friends my age who are in law or accounting, even finance.

Yep.

>Only ones who even come close are in non-white collar jobs with unions and access to lots of overtime hours that they pick up. Their base pay isn't even close.

Yep. I would say that SWEs have even better working conditions than any union I have heard of.

I found the books about Apple technologies by this collective to be very good: https://www.objc.io/

As far as I remember, the author of this book: https://www.amazon.com/Intellectual-Property-Open-Source-Pro...

Recommended a scheme to shield OSS developers from liability. I am not a lawyer, so it looked a bit overly cautious to me, but it seems that was a good idea.

See the chapter 14 called incorporating as non-profit. He mentions a case where Gaim (a messenger software) developers were sued by AOL.

We have been working on a VS Code extension (link in my profile), which released some time ago. I had a thought that may be we should stick with the approach used by most of the ecosystem, when license is linked from the extension page. However, we decided to show accept/reject dialog. I am glad that we did it this way.

I have seen a large number of products (from SaaS to desktop apps) which don't properly ask for license acceptance to reduce sign up friction. They might be affected in the same way (I am not a lawyer).

This is irrelevant, since the theory is that a fiduciary duty exists completely absent any interaction, and any payment, whatsoever, or in the event literally anyone else pays you to do the work (including your employer), you are now a fiduciary of everyone who uses your software in any financial sense whatsoever.

So do you mean that limited liability clauses essentially void? This looks really absurd. How could we develop and distribute any software in such a context?

This is very good news for us as consumers. We don't want anyone of the players to dominate this field, and we want the service to be as cheap as possible, ideally free.

It will essentially still be locked away by an oligopoly that has little distinction among the participants. The influence on society held by that oligopoly will significantly surpass the current concerns of social media.

For much more in depth take, I wrote recently about that here. https://dakara.substack.com/p/ai-and-the-end-to-all-things

API access isn't what we want. We want to run those models ourselves.

Almost all players in this field publish their work. If need arises we will be able to reproduce them, but only large company will be able to run the models cost efficiently, and there're a lot of scale effects here.