170 karma · joined February 29, 2024
It makes PHP easier to rely on. Not only is it rock solid and easy to use, but now it has a long lifetime.
Not to say upgrades are bad, but sometimes businesses don't understand the value in updating things...
Long live PHP!
I'd love to hear more about the product though! Without giving too much away, what does the product/company do? :)
Some more suggestions for open source components:
Redis for caching and queueing SMTP for mail Nginx for load balancing Cron for scheduling
I'm going to use the LAMP stack for example, because everyone is familiar with it.
For example, if you choose MySQL (rather than AWS Aurora) you can:
1. Run that locally during development
2. Install it yourself on a VPS
3. Or migrate to any of the big clouds quite easily
Same goes for your stack. Rather than using PHP with AWS Lambda, provision VMs and install PHP yourself (probably using some sort of shell script).
All cloud providers offer a VM in one form or another, so you're free to swap to another one when you choose.
Thank you for summarising why I hate agile so concisely.
I don't hate agile itself, more the clueless people who think agile replaces requirement gathering and planning.
Really nice device and the price is good too.
I've never connected mine to the internet. I just use it as a giant USB stick with a screen.
Not that I've needed to, but you can take it apart and increase the storage too!
Don't get me wrong, it's very simple, but it was fun.
Felt like using Flash again. :)
If you've got physical hard drives to back up to, and you want to be able to use those hard drives on Windows, Mac, and Linux:
It would seem a good file system for cross compatibility is exFAT.
While it doesn't have all the features of other file systems, it seems to work on almost everything without making too many compromises.
Something to consider if your main computer dies and you need to restore from a backup using a different OS!
I hope this helps someone. :)
The thief won't care if you tell them to stop. But their domain registrar, web host, video host, social media accounts, and payment processor will care about copyright infringement.
If multi-tenant things get complicated quite quickly. It may be worth looking into existing packages/libraries for your stack. I would be careful about using a third party service for this due to the latency it may introduce.
If not then just have a FEATURES constant. The value can be as primitive as an associative array, dict, hashmap, or struct. The keys are your flags and their values are booleans.
Not your forever choice, but very simple, quick, and easy to use.
https://www.amazon.com/StirMATE-Automatic-Variable-Self-Adju...
I wish TSVs were more popular though. Tabs appear less frequently than commas in data.
My biggest recommendation is to avoid Excel! It will mangle your data if you let it.
1. Digital Ocean offer small VPS for $5 per month. That's a 50% saving right away!
2. Stick with Ubuntu in the beginning. It's not the best, but it's 100% good enough and has so much support and tutorials out there.
3. If you have a small VPS with not much RAM, definitely set up a swapfile. It gives you virtual RAM for doing RAM heavy things on a small VPS.
4. Use the virtual firewalls offered by your host rather than the server firewalls in the beginning. If you mess up a server firewall you may have to get your host to reset it for you. If you mess up a virtual firewall you can amend it through a web UI and get back to doing things quickly.
5. Learn to read man pages and log files. Between the two you can figure out how to do stuff, and then figure out why it isn't working correctly.
6. In terms of security, use a recent distro, use a firewall close everything you don't need, use SSH keys, and set up secure passwords for everything else, and you will avoid a lot of problems.
7. Keep an eye on resources, programs like top, uptime, free, df, and du will allow you to see what's using up CPU, RAM, or disk space.
8. Learn a relational database. MySQL or Postgres are good choices. This skill will keep you employed for years, almost every business uses a relational database in one way or another!
9. Have fun :)
If you know Python, use Django for full stack and FastAPI for APIs.
Although Go is great, I wouldn't add another language into the mix. Just not worth the overhead given that you can do so much with Python.
Also, try using boring old server side rendering as much as is possible.
Not to rag on Svelte specifically, but you'd be surprised at how far you can take a web app before needing to adopt a frontend framework!
The only answer that makes any sense here is Ansible.
Arguments:
Way simpler
Can fall back to using plain SSH if things goes really wrong
No vendor lock in
One less bit of technology in the mix to go wrong
Very boring, which means very reliable
I only install Redis on Ubuntu VMs. I don't pay for hosted Redis (since it's always been rock solid for me).
Will these changes stop me from running `sudo apt install redis`?
However it relies on two important things:
1. Using something which uses the OS's built in browser (rather than something like Electron).
2. Keeping your JS very lightweight.
This was shared a few days ago, combined with py2app could be a winner:
I trust Redis to not do something weird with their licensing or pricing in the future.
Plus Redis has billions of production hours under its belt.
It's easier to install and understand.
- Can all be run off one big server
- No licenses or costs
- Super stable and battle proven
- Deployment, development, and debugging is stupidly simple
- If you don't want to do your own server admin there are millions of hosts
- Everything can be solved by Googling and copying and pasting
- Developers are easy to come by
- Frameworks such as Laravel and Symfony exist (not that you have to use one)
Remember, you said easiest... not best. :)
* Although "best" is subjective!!!
Is this production ready? I need to target Windows and MacOS with a high level of stability.
2. Realising that complexity is the enemy. Smart people avoid complexity, dumb people who think they're smart introduce complexity.
3. Realising that in order to ship anything worthwhile you need good specifications, a clear line in the sand, and the time to be left alone to do it.
Edit:
4. Shipping something small is good. You don't know what is needed, but once you've ran something in production for a few days you probably will. YAGNI and MVP all the way!