226 karma · joined July 20, 2018
If someone wants to me read a giant text generated by a small and poor prompt, I don't wanna read it
If someone wants to fix that by increasing the effort and do a better prompt and express better the ideas, I rather read that prompt over the llm output
I know there are people still using PHP 5 and deploying via FTP, but most people moved on to be better professionals and use better tools. Many people are doing this to AI, too, me included.
The problem is that some big companies and influential people treat AI as a silver bullet and convince investors and customers to think the same way. These people aren't thinking about how much AI can help people be productive. They are just thinking about how much revenue it can give until the bubble pops.
A static site/blog generator written in c++.
I initially made it with markdown support for my blog but latter I've added also templates based on json for another project.
- git: More productive and more control over the code base and the each member team responsibilities. Don't change the structure of the code. If it's a monorepo, leave it as it is. Just create simple branches like, prod and dev. Consider putting nginx configuration into the repositories as well (since it's part of the application).
- Documentation Via Comments: In this part you should improve a little of culture in this team, new code should be documented at least using comments.
- Test environment: now you have a dev branch you can push all the code to this new test environment and test things without worries. If it's possible start to write configuration environment case it's needed.
- CI/CD: now everything is traceable by git, you can write a routine to deploy every branch on it's place. Some tools self hosted you can consider: Jenkins or Drone.io are great and requires almost no maintenance(no need to hire a devops to work on this)
- Database: you have test environment and ci/cd, now you can TEST(what a great news) your database migrations. In php I can remember of phinx to starting to write migrations for this application.
- Auto Tests: I think unit testing could be considered when adding new code. Old code just leave as it is.
If you apply at least 3 things of this list I think at this point you will see that's a rewrite could be not that necessary.
Unlikely IE, edge its been a widely used browser since its good as chrome so people don't have the need to switch browser, so it have to be tested
Now we can expect apple release safari to linux? I don't expect this so soon.