HN user

Curzel

133 karma
Posts15
Comments60
View on HN

Yep, it's mostly garbage, I feel like I woke up with hangover honestly.

No AI writing in the book so far (but that does not mean it won't be garbage anyway lol)

GPT-4.5 1 year ago

I have no idea why they bothered releasing it, but, as we saw with the other models, they will eventually release a 4.5-turbo (or a 4.5o) of sorts that is in line with current pricing

Started with the idea of generating comics with GPT4 and Midjourney, ended up with an animated show! The results are both surprisingly good and very, very cringe.

In this post I explain the basic concept, thoughts?

Before you say it: The idea is not to put together an automated content farm, I'd like for this to be a tool I can use to develop more consistent stories in the future.

Dead, but we're heading into new a new paradigm of hardware accelerators (encoders, decoders, AI-optimized chips, multi-die GPUs, ...) and new packaging systems (M1 SoC's, GPU Chiplets, ...), all powered by what was previously the big bottleneck, interconnection within these components (AMD's Infinity Fabric, Apple's UltraFusion, ...)

I don't get it.

People have been wondering when this would happen since the very first iPad Pro, so lots of people will be happy now...

Even assuming all the required horse power is there, I still don't get it...

Maybe I'm getting old.

Layoff was probably 50% accounting for another chunk of people leaving soon after, so that staff reduction will be 60-70% in total.

Also, I don’t think the majority of people even work on core products.. for example, did you know Twitter implemented their own OnlyFans competitor? It never launched afaik

Step 1 is to trim as much as possible and consolidate core functionality…

Step 2 is back to profitability.

I understand that, let’s see if it works

What is your true objective? What will you be evaluated on?

Focus and think of any other improvement you could do.

It sounds like management doesn’t think there is an actual problem to solve, so I wouldn’t necessarily pick refactoring or rewrite as the hill to die on.

If you go the refactoring route, i have little advice:

0. Clean up the database, it will immediately impact performance and make management happy

1. Find vertical (feature-wise) or horizontal (layer-wise) architectural boundaries and split the code base into module, separated libraries. This will be an ongoing process for a long while. Do it by touching as little code as possible - this is pure scaffolding, actual refactoring comes later.

2. Stick with PHP, at least until results from #1 aren’t good enough.

3. Use testing as a tool to pressure management, it works a surprisingly large number of times

4. Rewrite one feature/page at a time, once results from #1 indicate a good candidate. It might be a good idea to introduce a new language at this point, or even some form of micro services (if it makes sense).