946789987649

I didn't know places still had quarterly releases. That seems to like the one to resolve rather than a mono repo.

Yeah agreed - does anyone really care for $4/month?

You could say the same about Google, where there's an entire generation who no longer needed to trawl through encyclopedias to find relevant information. I think we're doing just fine.

I think the question is why rather than physically how. Surely that amount of tabs is useless because you'll have duplicates, irrelevant things, etc.

I've had a few people chuck the entire problem into ChatGPT, it was still very much useful in a few ways:

- You get to see how they then review the generated code, do they spot potential edge cases which the AI missed? - When I ask them to make a change not in the original spec, a lot of them completely shut down because they either didn't understand the code generated well enough, or they themselves didn't really know how to code.

And you still get to see people who _do_ know how to use AI well, which at this point is a must for its overall productivity benefits.

What do you do if a junior asks for help and it's easiest to code through with them?

Going through our pre-seed round atm and it is incredibly frustrating. I haven't raised in the US so it may be similar there, but the amount of time wasted for a relatively small amount of money is painful.

I'm also not sure what the government can do. SEIS/EIS is a great scheme, but the SEIS limit of £250k feels almost too small to do anything meaningful, and EIS funds are generally later stage or re-investment from SEIS.

You could argue similar for US/UK, but I would still rather live in the UK.

Not sure how you gleaned that it was lower quality from my post?

You can move fast and still do things well if you set it up correctly at the start. Specifically with things like automated testing and so on.

I've always been a backend developer, but started my own company about a year ago. From that, I had to become full stack and AI has helped dramatically with the learning and implementation. There's a lot of things which would have simply just taken far longer to understand or fix with just stackoverflow/google.

And that's just on the coding side, even more on the actual start up side!

Bugs and infrastructure are two different things. Yes when a game first launches it will potentially be quite buggy, but every expansion until recently has been impressively slick.

Even World of Warcraft which used to be seamless in terms of issues, has had increasingly more and more obvious bugs. A sad state from the "Blizzard polish" of yesteryear.

Of course people forget things, but as the other commenter mentioned, I think you are bringing unnecessary logic to what is an emotional subject and response. Which as they say, makes you come across as a jerk while bringing no value to the conversation.

I had a manager do something like this but in a slightly better way. Each week we took it in turns doing our "life story". Some did it funny, some did it really personal and serious, some more of a CV, and some a mix of them all. You could really decide how you wanted to do it, and people got to know you a bit better.

Sounds a bit like plastic surgery... you only notice the bad ones.

accidentally hitting each other

You could argue the same for timezones in a date library, yet they have them. I would think a library dedicated to money will in fact be the most up to date.

Even as a one person developer, you inevitably need to come back to old code and understand what's happening. Types help with that. The size of the team or codebase is irrelevant.

It can be even better - in the UK unless you earn over a large amount, or know for a fact you have some special circumstances, you never have to do a thing.

We had something similar at an old job. It was pretty nice as then you were allowed to release your changes whenever as long as all the changes up to yours had been tested.

> You'll get diluted, replaced and kicked out the moment traction starts gaining.

This is just straight up wrong. You don't HAVE to enter the VC cycle of endless raising, and if they're wanting to replace/kick you out, what are you doing wrong?

> eventually jump ship and become a captain of your own vessel.

That's literally what being a co-founder is. You might be even split with someone, but you are still very much the captain.

> Jooq isn't bad, but it's not SQL, it's Java trying to be SQL.

Can you elaborate on this? I have been using JOOQ for years (with Kotlin), and I have never had any issues with it "trying to be SQL".

That's a pretty short journey (probably about 15 minutes), but yes it will definitely be a lot better now. I think also part of it comes down to 1. getting used to it, and 2. the time you cycle at. Rush hour, while more hectic, actually is quite a bit easier because you're often going far quicker than any cars.

We already have people editing videos anyway, you never see the first cut. AI-matically removing umms is really just speeding up that process.

JOOQ is the only acceptable ORM.

> the ability to view lyrics while listening to music

You can still do that? Am I missing something?

Is there a reason Linear can't be used by companies later than start up?

Sounds like who you're targeting right? Big corps don't need generalists, start ups do.

That page continues to just get worse and worse. Truly awful.

> developers insist they cannot write SQL to fix that, because it is somehow impure :-)

Because then they lose many of the benefits of why they used an ORM in the first place. Though I am a big fanboy of JOOQ for exactly this reason.