Serverless will forever be stuck as a tech that’s only good for majority async stuff because of cold boot speed, scaling costs, and general latency.
I’m learning Scala, is that close enough?
Language absolutely is a marketable skill because most companies are looking to hire someone who can start working day one not someone they’ll have to train for weeks or even months in a new language that heavily relies on some specific framework.
Jira is a pain, slow, bloated, and ugly.
Trello okay is for student projects, too basic.
ClickUp was decent when I used it professionally, I still use it for personal project management.
Azure DevOps is baby’s 1st JIRA, but somehow Microsoft made it worse in every way.
I find that code written towards fulfilling some specific database design is usually a nightmare about 20minutes into the project. You end up with garbage semantics and interfaces because you’re building an entire app for the sake of storing stuff in a database. It’s an ass backwards approach to software development imo, software is about solving a human problem and data persistence is just one of the steps in the solution. Instead figure out what data your consumers need, then figure out what domain objects can be extracted from that, then plan how you will persist those domain objects. You’ll end up with less boilerplate, better naming of entities and services and you’ll also find that the words your team uses to talk to each other make sense to your business people not just your dba.
Microservices and document db’s go brrrrrrr. Data duplication is completely fine as long as there is only one source of truth that can be updated, all copies must be read only. Then the copies should either regularly poll the source or the source should publish update events that the copies can consume to stay in sync. It’s simple stuff but keeps your system way more available and fast than having multiple services talk to a shared db or worse, multiple services constantly fetching data through a proxy.
There isn’t one, java is excellent for async and multithreading and it does it properly unlike node that fakes it by running on a single clever event loop or stealthily launches a bunch of node instances in the background depending on implementation.
Op comes off a bit, uninformed. E.g. I use docker engine and docker compose inside WSL2 on windows and performance is fine, then I use Intellij to manage images/containers, the service tab handles the basics. If I need to do anything very involved I use the cli.
Docker is fine, the docker desktop panic really only revealed who never took the time to learn how to use docker and what the alternative UIs are.
Surprised how little love this option is getting in the comments. Not only will swagger be generated for you from your openapi spec, it has a clean fast UI and shared auth.
Legacy code is just code inherited from developers that are no longer around. It’s quality has nothing to do with its age.
Comparatively to the rest of the western world, western Europe dev salaries are garbage.
I live in the UK and have friends in Germany, France and Norway. Senior/mid salaries are fairly similar, so is the cost of living. But, I could get the same job in Poland by taking a 10-15% salary cut, living there my cost of living would go down by approx 40%. I would be noticeably wealthier there doing the same job I do in the UK.
Same story for many eastern european countries, they pay better for skilled labour but way worse for unskilled labour.
The only thing keeping me here is family and friends.
Yeah, that’s great, until you need to conditionally compose a query. Suddenly your pre baked queries are not enough. So you either:
You write like it’s ORM vs native. ORMs let you write native queries and execute them while also doing all the tedious work for you such as:
So if you love native queries write native queries in an ORM which will do all the tedious shit for you.