Engineering Thoughts

- Deadly sin number 1:

Companies are mostly looking for framework or library “monkeys”, not software engineers. They do not understand technology in general and just follow whatever is trendy in the industry at the moment. They are not concerned in hiring highly skilled people capable of solving an infinity of technical problems and build “on-demand” solutions, independently of the tools used to achieve success. Instead they just look a certain number of years “in contact” with tool A, framework B, or library C. They don´t understand that every tool has his “pros” and “cons” and that a good software architect can make fire with a variety of instruments, not just with a lighter. A “framework X” developer is NOT a software developer, much less a software engineer. These last ones are an endangered specifies in a world where “fast” and “easy” seems to be the rule. “- Sorry you cannot consider your application, because it seems you´re just used to drive BMWs, and we need a Mercedes driver”. “- But sir, these are all cars, and i know how to drive any type of car, i´ve been a taxi driver for so many years”. “-Sorry kiddo, no can do…” Sure, you might get a good start, and move faster for a couple of weeks, but on the longer run that´s probably not the advantage you were expecting, and you might get surprises too. People can always be surprising, that´s part of our evolutional nature. If you think it is more important to know a specific library than the underlying programming language and concept (that might already exist for a decade before this library was even created) then i believe you have a big problem.

- Deadly sin number 2:

Companies often confuse years or “getting in contact” with a given programming language, a given framework or a particular library, with the level of expertise in each one or the level of expertise of the candidate in general. Just because someone is working with a given tool for 5 years or has been developing in a specific programming language for another decade, that does not necessarily makes him more capable or efficient than someone who is doing the same thing for only 1 year, or even just a few months. Time spent on a given job is not equivalent to better or lesser skills. That is completely ridiculous. I can be a teacher for 50 years and that does not necessarily makes me a good teacher, on the other hand, someone really skilled to teach that has just started can be considered a better teacher by their students, or no? Why would it be different with software? Makes zero sense! The last thing i want to remark is that there is a big difference between a programmer, a software developer and a software engineer. These are not synonyms people! Do your research if you confuse these often.

- Deadly sin number 3:

IT Recruiters do not spend enough time checking the candidate´s background, his skills, or his particular job or technology stack preferences. Very often they just randomly “shoot” dozens of emails to anyone that shows up on their Linkedin searches with the keywords “software” and “developer”. That´s probably the reason why 90% of all direct messages refer job “proposals” where the requirements do not match the candidate profile, skills, or preferences. From my personal experience i can say for sure this is true in 90% or more of the cases. For instance, on my profile i make it very clear that i am only open to remote opportunities, nevertheless 50% of the direct messages require relocation and “on-site” work. Just read the fuc***g profile! Is that too much to ask? And i have some fresh news for you IT recruiter, yes you… the one reading this list; “Remote during Covid-19 pandemic” is NOT remote work!

- Deadly sin number 4:

Feedback, or the lack of it! Roughly 8 out of 10 contacts do not provide any feedback. They ask you for contact details, they ask for your CV, they ask to to fill some form or skills questionary, they might even ask you about your pet name. What they immediately want you to do is to “jump” into phone calls. Despite they hadn´t disclosed any relevant information on their side, except they are looking for a monkey that “knows” how to handle tool A and tool B. So, we do that, and we waist precious time just to never hear from them again. Not a “Yes”, neither a “No, sorry”, nothing! They are always in such a hurry to grab every single piece of information from you, but as soon as they have another (perhaps more promising) candidate, they instantly forget about you and pursuit the next victim. Many times you only figure out that the job is not interesting for you either, after diving into more deep on the process itself. Shame on you IT recruiter! That´s why developers in general do not like you that much.

- Deadly sin number 5:

Use an IT recruiter or a “specialized” IT recruitment company. Yes you read it right, it´s not a mistake or a typo. Do companies do not have HR departments anymore? It´s 2026, not 1990. Every company should have their own IT department anyway, with people qualified enough to handle or at least help on the process. Why all of the sudden every single company needs a “middle man” to hire a new employee or contractor. Is your CEO, IT or HR director not smart enough? Is it because your company does not speak “tech” dialect at all? Well, that can be a real problem if we end up “matching”, cause we will be talking different languages.

- Deadly sin number 6:

The technical / code test. Oh my God, the test! This is probably the worst of all. I will dedicate another entire article to this one alone.

I have no idea when or where this trend started, i guess it was somewhere in the last decade, probably in some sh**ty company, but let me say this is a complete nonsense for so many reasons that i cannot even remember them all. The main reason would be that we are about to start a business relationship where one of the parties simply does not trust the other and it clearly states it right from the beginning.

I´m the recruiter or someone representing the hiring party, you´re the developer. Your CV looks impressive, you have lots of apps on Google Play and And Store, i can see you´re really active on Github and similar platforms, but you know what? I do not trust or believe you. I see you have built all these apps and websites that i can easily check, and you say you have been working with Java and JavaScript languages for almost 20 years, but nevertheless i want you to make me this test app, for free. Cause i´m pretty sure you have nothing else to do, and we all know that all developers are simply nerds that love to write code for free and have no lives whatsoever. Don´t worry, it will only take you a week, and i have to make sure you really know what you say you know. What could go wrong. Worst case scenario, i don´t select you for the position, neither i contact you again or provide you any feedback about the outcome. Sure, this makes perfectly sense. Just like when a neurosurgeon is applying to a new Hospital he is first required to perform a brain surgery, for free, just to see how it goes, and to double check that instead he is not just a regular soccer player pretending to be a doctor. Why would software be different than all the other jobs in the world? I know, for no reason! Still, it is, for whatever reason.

- Deadly sin number 7:

Sins 1, 2, 3, 4, 5 and 6 altogether. Ok, i know, this is not really a sin on itself, but believe me, it happens, and i was not really sure about what to write here so... The items here listed are just some examples of what i think is wrong with tech recruitment these days. It´s not just the process but also the persons that are doing it. Everything seems way to focused on short term results, way too focused on technological trends that may come and go every year. Everything is so “standard” that leaves no room for innovation. Nobody is looking at the larger picture or timeframe. I cannot hardly imagine how young people leaving universities struggle to find a job in this industry. Sometimes it can get so ridiculous that they ask for more years of expertise on a given tool than the years that have passed since the tool was created (yes it happens, a lot). On the other hand if you have a broader expertise then is not so good either because you have not spent enough years working with the same tool, one of those currently listing on the top 3 of the “most popular”. We all know that to be a good professional in any medium you need to be doing the same thing for many many years, right? Or isn´t it?

Final thoughts

The Internet that started as the land of the free is becoming more centralized each day, and it almost seems that nothing else existed before giants like Facebook or Google stepped in, because we are forced to learn and use the tools they have created for their own specific internal needs, like if there were no other alternatives, and like if they were the only and true keepers of all the knowledge that exists. Sorry, but this is just too crazy to handle! The only explanation that i can find is that companies prefer a legion of blind “doers” that don´t think, instead of a legion of “thinkers” that can do (and do better). If they don´t know the effects of that on productivity and efficiency, on the long run, then i humbly suggest a little bit more of research before moving onto the next recruitment process.

I have to conclude that most companies are not actually looking for software engineers, they are looking for people with basic software development skills to follow whatever rule is feed to them, without questioning a single thing.

Next time, probably is also a good idea to focus a bit more on the candidate´s skills, in what he has already achieved and in what he is expected to achieve, given his skills or background experience. Consider also his personality, how he adapts and faces challenges, and how you think he will fit the company mindset as well. Don´t just overlook in search for a bunch of specific tool keywords on the CV. Just because he is using some fancy tool for more than 5 years, it doesn´t necessarily means that he doesn´t suck at it anyway. Of course, this is not a thumb or rule but you get the idea. By the way, those can easily be faked too, you know... Tools come and go everyday but people stay and also adapt and evolve. A good engineer will be able to build anything with any tool. It doesn´t matter if it has to be done with React, Angular, Vue, with SomeCrazyFakeFramework not yet invented, or just with some wood stick.

Choosing to glue your project (and your team) to a very specific set of instruments might not be the best idea for any side. Anyway, these are just my 2 cents, or in this case my “7 deadly sins” handbook.

1 — Laziness.

Don´t get lazy. This is the number one priority. Just because you´re not at the office and nobody is watching you directly, it doesn't mean that you shouldn´ t be professional. On the contrary, exactly because no one is watching, you should work harder and proof your work. Take ownership of tasks and deliver the best you can in time. Work the same amount of hours as if you were on the office. Feel free to take short breaks as usual, they are necessary, but follow your schedule as planned. Don´t cheat, cause sooner or later it will came back to you.

2 — Wrong or busy environment.

Don´t work on the couch or in front of the TV. Get yourself a private room. Turn one division of your house into your own office. Go to some coworking space, at least from time to time, if you are lucky enough to have one nearby. Follow the schedules (again). Don´t sleep until 10:00 am, just because you can compensate in the evening. Do the regular nine to five if it's a full time job. Take the regular one, one hour an half to lunch. Again, be professional and act as if you were surrounded by colleagues.

3 — Browsing Social media.

Avoid social networks browsing at all cost. Twitter, Facebook, Instagram and similar, are pure weapons of distraction. Don´t open more browser windows than the ones you need for your work. Its very easy to get distracted if you´re not carefull. Turn off website and phone notifications. Focus on your work and be productive. Procrastination is your number one enemy. Use your lunch break to scroll through pictures of cats or dogs, or to connect with others if you have too.

4 — Overconsumption of food or beverage

Try to stay away from the kitchen or the refrigerator. It´s very easy to drink and/or to eat in excess when you have the stuff at the reach of your hand. Normally, on most offices, you either have to pay for your food or it is simply inexistent, what naturaly restricts its comsuption, but when you are at home its all in reach.

Its ok and even recommended to take short meals two or three times a day, but do it during your small breaks, faraway from the computer. That´s why the breaks exist too, you need to clear your mind and rest your brain from time to time. Don´t take food (specially food) to your desk while you´re doing work. You won´t notice the extra calories intake. It's not good for your health neither for your pocket. Now, about that coffee, i might disagree there.

5 — Lack of exercise

Stay active. It is very important that you do some sort of exercise, if not daily, at least 2 or 3 times a week. This could be a simple walk in the park, a short workout on the local gym, walking your dog, do some jogging, etc… The point is, that it doesn´t really matter what you do, as long as you´ re committed to do something.

If you´re not commuting you´re automatically becoming more sedentary. I would advise to workout on the morning. At least that seems to be what works best for me, but each person might have a different physiology. I always feel more energised if i start my day with some activity. Having a morning shower before starting to work might also be a good alternative. Whatever you do, just don´t get out of bed and immediately sit in front of the computer or desk.

6 — Try to chew more than you can bite

This is another golden rule. I know it can be tempting to have more than one job as you have the freedom (most of times) to manage your own time. But is also very important that you don´t take more tasks or projects than the ones you can confortably handle. If you are rolling a full time job i would not advice to take any other offers that might appear, unless is some part time gig that you can deliver after the regular work hours or even at weekends (i would also not advise to work on weekends nevertheless, they exist for a reason; to have some rest and enjoy life).

The only occasion i would feel confortable to have more than one job at the same time is if both are part time jobs that do not overlap with each other. Overlapping projects can be exhausting and confusing, specially if you work on completely different things that require different tools or technologies. It will mess up your brain and you will need it to stay sharp and focused, specially when you´re not interacting with other people directly. Perfectly executing different multiple tasks at the same time is almost impossible. Something will eventually suffer.

7 — Work in your pyjamas

You should never work with your pyjamas on. Some studies made during the pandemic found out that working from home in pyjamas does not lower productivity. However, it could be linked to a poorer mental health. I´m always a bit skeptical about these studies because it depends a lot of the person, and his natural predestination to adapt to a remote work environment. However i strongly believe that you should keep your working habits as clean as possible.

I would say it is allowed to wear more comfortable clothes (there is no need for a necktie obviously) but never ever stop dressing yourself to start working. Remember, the goal is to do the same exact routines as you would do on a regular job at the office, with the advantage of having a little bit more freedom and less stress (only if you manage it correctly). Wearing only pyjamas and sandals is not the way.

And this concludes my top picks. There are a lot more “dos” and “don´ts” in what concerns to remote work, but like many things in life this is not rocket science. What works for one person might not work for the other. Its up to each one of us to find out what works best. Its a neverending learning process. After more than a decade working from home, i still find myself learning and improving from my own mistakes.

1 — Always have a schedule.

Even if you´re not really an employee of a third party company, and you´re just working on your own, as a freelancer, contractor, whatever… always, but always have a working schedule. Even if you´re not doing the standard “9am to 5pm” day you should have a “regular working day”. Do not work whenever you feel to, do it as if you were at the office. Personally i do the regular working schedule (or close enough anyway) and i take the standard 1 hour to lunch. Of course, there is always room for some flexibility but don´t move too far from the track.

2 — Always have a proper working space.

Even if you´re working at your own home, you should always have a dedicated room. Do not work on the couch, on the kitchen, on your bedroom, etc… Do it on a separated and dedicated division. Make it comfortable, personal, and cosy enough, but without unnecessary distractions.

3 — Avoid distractions.

Avoid any distractions that you would not normally have while working at the office. So for instance Television and Social Media browsing are completely out of the question. Stay focus and stay professional. Even if no one is watching you (yes, i know, there are also those “remote workers spy software tools”… and i´ll deal with those on another article) always do your job as if you were in a room full of other people watching. Remember, it´s called remote work, so you should be working.

4 — Take small breaks.

When working at home is also very common that you forget to take the necessary breaks. After all there are no colleagues inviting you and you are so comfortable that you might even think that you don´t need those breaks. This is particularly important if you´re seated and staring at a computer screen for many hours. It´s not good for your health and if you were at the office you probably would be doing the same breaks; for a coffee, for a cigarette, for a glass of water, etc, etc. So there is no reason why you should not be doing the same. Neither more, neither less, just keep doing it the usual way.

5 — Exercise. Take care of your body and mind.

Having a workout routine is also very important to keep you mind and your body in shape and harmony. You´re not commuting, so you probably will be more sedentary just because of that alone. Either go for a short walk, run a little bit, lift some weights, got to the local swimming pool, whatever. Do whatever you enjoy the most, but do something. Personally, i have a small gym on the garage and i like to lift some weights after breakfast, but on some other days i just go for a short 30 minutes outdoor run, slow paced cardio, empty stomach. That´s how i like to burn those extra calories. In my opinion the best time of the day to workout is right after getting out of bed, and so before starting to work. I guarantee you will feel more energized throughout the day. Do this at least 3 or 4 days per week, if not on a daily basis.

6 — Eat healthy and stay hydrated.

It is very easy to be tempted to hit the fridge or that crispy cookies package more often than usual, just for the sole reason that they are more in reach than they would be while working at some office, and nobody is watching right? Well, that is not so good for your health either, so pay close attention to that. Do not break neither cheat your normal diet. In fact, if you have your own food around, this is probably an advantage, as long as you make the proper choices, unlike while at the office, that you cannot actually change much of the environment. There also some useful mobile apps that can show you reminders and keep you on the right track, either for eating, for drinking, or just to tell when is time to take the ass of the chair.

7 — Find the perfect spot.

Last, but not least. “Remote work” is not exactly the same as “work from home”. Most jobs these days only require an Internet connection. This is particularly true on my area (IT and software development). So, from time to time it is also good to move your office to some other place, and change the view, sort of speaking. These days is very easy to find free Wi-Fi hotspots everywhere, or you can also take the Internet with you on a small and costly USB drive. Rather you are on a big city or in the middle of nowhere it is not that difficult to find a nice and quiet place where you can do your work. You can do it for a single morning, for an afternoon only, or do it for an entire day.

There are more good habits that i know of and that i could add here, but i think these are probably the most important ones to keep you on the right track. If you´re just starting i´m pretty sure these basic rules will make the transition easier for your. And if that is realy the case and you´re new to remote working then let me say: Welcome to the revolution! Enjoy the road ahead cause this is the road of the future!

If you like this article please share it with others. Have a nice day and grab a coffee!

The Challenge

When you're building infrastructure that needs to work across Ethereum, Polygon, and Solana simultaneously, you quickly learn that "move fast and break things" isn't a viable strategy. Every decision compounds.

The real challenge isn't just handling the load—it's maintaining consistency across chains with different block times, gas models, and finality guarantees. Traditional database transactions don't cut it anymore.

What Actually Works

Event sourcing. Not the buzzword version—the real, unglamorous work of treating blockchain events as the source of truth and building everything else as projections. It's more code upfront, but it saves you when things go sideways (and they will).

We ended up with a three-tier caching strategy: Redis for hot data, PostgreSQL for reliable reads, and direct RPC calls only when absolutely necessary. The trick is knowing which tier to hit first.

The Human Part

Technical architecture is only half the battle. The other half is building systems that your team can debug at 3am when production is on fire. That means logging that actually helps, error messages that point to the problem, and documentation that people will actually read.

The Abstraction Trap

Tools that promise to abstract away complexity often just move it somewhere else. You trade understanding your database queries for understanding someone else's ORM magic. You trade HTTP debugging for middleware configuration archaeology.

Speed vs. Velocity

Moving fast is easy. Moving fast in the right direction is hard. Every abstraction layer you add makes it easier to build the wrong thing quickly. Sometimes the best productivity hack is understanding what you're actually building.

I've seen too many projects sprint for months only to realize they built on sand. The foundation matters. The details matter. The craft matters.