133 karma · joined April 25, 2014
No AI writing in the book so far (but that does not mean it won't be garbage anyway lol)
(Original comment was not a joke btw, it's part of another thing I will publish eventually)
/compact we will now work on x, discard y, keep z
I’ve being doing mostly mobile apps for the last 10 years, tried Rust for fun for a couple of months, recently tried C++ and I’m having the time of my life.
Btw, not sarcasm, now looking into C++ jobs
This is a good channel
https://chat.openai.com/share/2ec10eb6-a7f1-4b27-9f56-0ec7f2...
(share icon the side menu)
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.
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.
Btw, I'm looking into porting it to Windows and Linux, if anyone is interested... :P
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
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).