As a dev, I can feel how much easier to work with the codebase must be after migrating from scattered raw SQL queries to ORM. In my job I have a project with a similar problem and the transition is slowly going on for years at this point, still not close to being finished.
I think Linkwarden is fantastic but should be described and advertised more as internet archiving software than a bookmark manager. It really should be obvious to anyone that it’s downloading the webpages, not just saving links. I
I second this. Very light, feature-rich, configurable and works flawlessly. I use it for ad blocking, proxying all DNS requests to DoT upstreams, and local addresses in LAN and over Wireguard.
I guess I see your POV but what if the no seatbelt guy actually understood the lesson and will voluntarily buckle up from now on? It could save his life.
Seriously, once you commited something to the repo it’s hard to lose it. Unless you delete .git. But a this point frequent pushing has your back.
I know git can be hard to grasp in the beginning. It was hard for me too. I highly encourage everyone to put in the effort to understand it. But if you don’t want to do that right now just use it. Just commit and push. It will pay off.
Following tutorials and courses is definitely a very popular way of learning programming but I personally hate it. For me, the motivation was always a problem to solve, and programming was just a tool to solve it. Of course, you probably need to follow some kind of guided experience to gather the absolute fundamentals, but to get better you just need to apply this in practice.
The first ever problem I decided to solve with programming was organizing pirated video files into manageable directory structure. I knew almost nothing about programming at this point and my thought process was something like this:
Now, the most important part of this is to have an idea for a project which either solves a real problem of yours or just is exciting to you. Some examples of my projects:
When starting most of these projects I had no idea how to approach the problem. So I just searched the web until I knew it. In the beginning you will probably be searching and reading much more than writing code. But that’s a good thing! Programming (or rather software engineering) is not about typing out code, it’s about breaking down the problem into smaller chunks until you actually know how to solve each of the chunks with the tools you have at hand. Once you have this understanding, writing code is usually rather easy.
I’m pretty this applies to tram and bus drivers literally everywhere.
I mean, I am applying various kinds of science but I’m not actually doing any science so I’m not thinking about myself as a scientist. What I do is solving problems - I’m an engineer.
curl is obviously fantastic but for more complex ad-hoc requests I usually prefer httpie.