SEEKING WORK | Remote Work | Worldwide Availability (EU-based)
Strong fullstack software engineer with 20+ years of experience. Stack: Kafka, K8, AWS/Azure, Postgres, API design. Very experienced on JVM optimization and perf tuning.
SEEKING WORK | Remote Work | Worldwide Availability (EU-based)
Strong fullstack software engineer with 20+ years of experience. Stack: Kafka, K8, AWS/Azure, Postgres, API design. Very experienced on JVM optimization and perf tuning.
SEEKING WORK | Remote Work | Worldwide Availability (EU-based)
Strong fullstack software engineer with 20+ years of experience.
Stack: Kafka, K8, AWS/Azure, Postgres, API design. Very experienced on JVM optimization and perf tuning.
I wonder how does he actually work as a digital nomad. Internet on DB trains is massively unreliable, there are entire patches of country that are not covered by mobile signal.
> I wonder how does he actually work as a digital nomad.
I suspect the secret here is that a lot of people adopting this type of lifestyle produce really mediocre output and some way or another fit into the gaps at a large company that doesn't conduct aggressive performance reviews.
Everyone is different but I find it hard to believe that high quality code is generated from working consistently in that type of environment. Perhaps lots and lots of boilerplate.
Having met many people who work remotely and travel, you have everything from mediocre english teachers, grifters, programmers (good and bad) to over-achievers with successful lifestyle-businesses.
Lately I've been programming less and less with wifi while sitting at libraries and cafes without wifi. It's fine, just have proper dev environments, use isync for offline emails, download docs and learn to read manuals instead of stackoverflow.
Perhaps he uses tethering on his mobile. Or gets on with working for long periods without being distracted by continual distractions so that reliability of the network is less important.
The boy is 17. At that age you’re not that overwhelmed with people distracting you for no real reason. (Apart from parents, but that’s not work-related usually.)
So you can basically be offline most of the time. I envy that bliss, it’s so difficult to do when you’re much older, with kids, pets, and the family.
I noticed that you use the @Transactional annotation on class definition. This will create a write transaction for every public method of the annotated class, including read only methods. You should consider using readOnly=true for read methods.
Additionally, I would consider using two data sources, one for write queries and a read only ds for the Q part of CQRS.