tooltitude

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.

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.

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.

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

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

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.

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?

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).

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.

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's very useful for enterprises to have one solution like github. Github isn't the best in every fields, but overall it's the best offer (they have git hosting, continuous integration, bug tracking, discussion forums, hosted dev environment, and now code search). It reminds me of a bundling strategy used in MS Office.

That's very good :) You might mention it on the site, since many people will have the same question.

But will it be enough for you to maintain the system long term? For people who potentially could use your service this is very important.

vscode recently introduced a similar feature. It stores a pretty large number of versions of every file without direct commit to SCM.

Because it's too complicated for many users.

The question is how do you make money or plan to make money? Payment processing would cost money anyway not from you but from the bank.

AI is a subset of ML.

For example, SVMs, Logistic Regression, and Decision Trees are ML but not AI.

It's a pedagogic paper, not scientific paper. People who invent things, and people who teach the things so that they become main stream often are very different kinds of people.

It's part of the puzzle. You could also mention Schmidhuber who claimed that he invented attention a long time ago (didn't read his paper though, so hard to judge).

I would say that BERT was an incremental improvement (as well as many others). But the idea of much more efficient sequence processing was introduced in this exact paper.

The main contribution of this paper is that the authors found a very computationally efficient way to process sequence data. That was a real breakthrough.

The previous approaches, like LSTM, GRE, etc were also working well on sequence data, but were much less efficient.

If we take a look at people who grew up with smartphones, most of them prefer smartphone to computer. Though they still use computers, but more like a work device.

I believe full text search stay there, but ChatGPT like technologies will augment it.

It's a dialect of Lisp created by Paul Graham (He's also the author of one of the best Lisp books).

I believe that it's a misguided policy. LLMs are becoming a part of us like mobile phones, internet, google, messenger and multitude of other thinks before this. We should embrace this.

I could imagine that OAI could be leveraged for single features

That's a possible application which won't be easily copied by the large company. But the value of such features is quite limited.

I could imagine content moderation, or reading sentiment from user tweets about a company.

I am pretty sure that these services will be provided soon by large companies and OpenAI. They are generic enough to have wide market, and many of these companies already have expertise in them.

So, no content generation, as that would be unethical without disclosure of AI usage.

Why unethical? I think these systems could create real content which is useful to everyone as well as spam content could be generated by humans.

Site: https://www.tooltitude.com/

Download link: https://marketplace.visualstudio.com/items?itemName=tooltitu...

Project Description: Productivity extension for Go developers in Visual Studio Code. Augments official Go extension with a number of code actions.