hmillison

in reality the question is more so, can the AI do a "good enough" job to not be noticeably worse than a real person?

there's a lot more involved in senior dev work beyond producing code that works.

if the stakeholders knew how to do what they needed to build and how, then they could use LLMs, but translating complex requirements into code is something that these tools are not even close to cracking.

I'd guess "huge investment" in this case is relative. The maintainer is not spending a ton of time building features for the CLA tool since it's mostly "done" and so investing more time to build support for Gitlab would require many more hours of development than they're probably dedicating right now.

And i can imagine that maybe they didn't abstract communication with Github enough and would need to refactor the system to handle that as well.

Generally, i think it's not totally reasonable to expect them to do more free work to support use cases that the maintainer does not need. Since it's open source, we're all welcome to contribute back.

I support remote work, but moving out to a rural area is putting yourself at risk if you expect to get high software engineer pay.

There’s a lot more competition for remote jobs and you’re also competing with highly qualified candidates in lower cost of living places outside the US.

The city of San Francisco is ~10% of NYC's population so it's not a good comparison.

Totally agree with this and one of the biggest problems i’ve dealt with at early stage startups is employees from a big companies that couldn’t deal with bypassing certain things like this.

Totally agree with you that now that React has matured, I have dealt with a ton of shitty React codebases because it really is more of a library that doesn't inform you how to architect your app and thus lots of folks went in completely different directions. Additionally because some of the pitfalls of React can be unintuitive, it is tough to unravel these in a larger codebase.

However, I will say it has been much easier to make updates to bad React codebases than a bad jQuery codebase. The way React works tend to make it less difficult to reason about even if the app is poorly built.

according to the article, Turbopack is 10-20x faster than Vite. I wonder how they were able to edge it out so significantly!

I would argue that Hanoi is more touristy than Ho Chi Minh so this comparison just tells me the author doesn’t know what he is talking about

That's great news! I missed that in my initial skim of the article.

I have used protobufs and grpc on the web before. Maybe this project is the magic bullet that makes it easy to do, but in the past that typescript support from Google and 3rd parties (improbable eng) was lacking and there was little interest in making simple changes to make it easier to use.

On top of that, the increase in JS shipped to user's due to the size of the generated protobuf objects was unacceptable for anything that cares about keeping their bundle size manageable. Have you done anything to address this issue?

I was really excited to try out Facet at the start of the year, but I was disappointed to see that most of the opportunities were for full time work and there isn't a lot of contract work advertised!

a lot of people living those lifestyles are living off of credit cards or their trust fund

NYC is one of the only cities in the US with quality transit and really the main one where it's easy to live car free in many areas of the city.