How our company celebrates Programmers Day 2023
We've put together a handpicked set of our favourite programming memes, along with news on the skills some of us have been developing recently.
Today is the day we honour the brilliant minds who build the digital world!
Programmers Day falls on the 256th day of the year – a number picked because it equals how many distinct values an eight-bit byte can represent, and it’s the largest power of two smaller than 365. And what does it look like in binary code? 1 0000 0000. Smart!
Source: daysoftheyear.com
Programmers - you design innovation, you build solutions, and you’ve mastered code. Your commitment and creativity shape the way we live with technology. Being a programmer means continually finding your path through the complex fabric of technology. No matter whether you’re a beginner or have years of experience behind you, the pursuit of getting better never ends.
Our company puts a strong focus on developing skills continuously. People on our team write blogs, produce technical newsletters – our Scala newsletter and Data Times – take part in tech events, record educational video materials, and share knowledge in our internal tech presentations.
Last 365 days of change
The programming world has seen a lot over the past 365 days. Apart from new language versions being released, the largest revolution was most likely ChatGpt’s launch on 30th November. It completely transformed how people write code! Tools powered by AI are revolutionizing programming – they boost efficiency, cut down on errors and broaden what programmers are able to do.
Still, AI use has to be balanced with human expertise, because creativity, critical thinking and domain knowledge remain indispensable in software development, a field that demands continuously learning new things.
What we have learned this year
Just as we did last year, we’ve put together a handpicked set of our favourite programming memes, along with news on the skills some of us have been developing recently.
Senior Scala Software Engineer
What did you learn this year?
That’s a question with many dimensions, so let’s break the answer into the two that everyone knows: hard skills and soft skills.
On the technical side, I learned a great deal about Java, deepening my understanding of core Java topics such as compilation, concurrency and performance. I also found time to get to know JMH (Java Microbenchmark Harness) and learn how microbenchmarks are written.
On the soft skills side, I picked up a thing or two about IT projects and self-managed teams. I now have a better idea of how to contribute more to the team and support my colleagues.
Software Engineer
Meme source
What did you learn this year?
This year, my goal was to master type-level programming in TypeScript. There’s still a long road ahead, but I’m fairly happy with how far I’ve got. At my job interview, I hardly knew what TypeScript’s ‘infer’ keyword was – I’ve progressed a lot since then. I’ve now written a number of in-depth articles on the topic. I’ve also started the exciting adventure of building my own step-by-step evaluator for TypeScript types, which I intend to unveil soon!
The project I’m working on at the moment has been a great source of new lessons:
- We managed to migrate a multi-project repository into a full-blown Nx monorepo. Doing so showed us both the benefits and the difficulties that such a transition brings.
- I explored the Capacitor framework and got the chance to compare it head-to-head with React Native.
- I’m currently learning Apollo GraphQL for a future service that we intend to build with this technology.
It’s also worth bringing up our company’s internal learning initiatives, which have turned out to be extremely valuable:
- We run several reading clubs, and right now I’m taking part in one dedicated to cybersecurity.
- Mock architecture interviews have done a great deal to sharpen my skills.
- I’ve been lucky enough to join interesting frontend talks and plenty of other enriching activities.
In an environment like this, it’s almost impossible not to learn a lot!
Software Architect
What did you learn this year?
I got the chance to join a project whose team members had plenty of experience with… SQL. I saw some of the newer PostgreSQL features used in practice, for instance the MERGE keyword added in PostgreSQL 15. We also relied on Common Table Expressions (CTEs) (the WITH clause), among other things.
PostgreSQL is capable of more than you’d expect. Cloud providers, however, might not support every feature you need. Google Cloud Platform (GCP) only added support for PostgreSQL 15 in May.
Software Developer
What did you learn this year?
I was aware that microservices aren’t always the answer, but until then I had never experienced it in practice. After joining a project recently, I saw for myself that microservices aren’t always the answer – certainly not at the very start of a project, when lots of things are still changing. Our issue was that the microservices were in effect a distributed monolith, whose sole benefit was smaller repositories. In exchange, we had to deal with things like availability and communication between services.
Starting with a modular monolith with carefully designed, separated domains is definitely the better choice. That way, the monolith can later be split into microservices, and a particular part of the application can be scaled if needed. Following a trend blindly makes no sense.
Frontend Developer
What did you learn this year?
This year, I found out (the hard way…) that web security isn’t merely an optional protective layer - it’s an absolute must. My curiosity about it has grown. I began reading cybersecurity books, and we even discussed one of them in our company reading book club. Web technology keeps evolving, so we have to keep pace to make sure our applications are safe and can be trusted.
This year has certainly made me a more mindful developer. Ultimately, front-end development is about more than looks and efficiency.
Senior Software Engineer
Meme source
What did you learn this year?
This year, I began learning Scala along with its FP paradigm. It may sound like a cliché, but leaving my comfort zone (I used to be a Java developer) was refreshing (something I needed) and extremely rewarding (which I didn’t quite expect).
Stop wondering whether to leave the beaten track. Just go for it!
Senior Software Developer
Meme source
What did you learn this year?
I got an exceptional chance to serve as Technical Lead on a large project for a U.S. corporation. Part of my job was managing a team of gifted specialists.
A central part of the role was setting priorities and deciding what mattered most for the project. Rather than handing out specific tasks, though, I concentrated on building an environment in which team members could decide for themselves how to reach these goals. That demanded not just technical skills from them, but also a sense of responsibility and the ability to organize themselves.
Throughout the project, I had to align our work with other teams handling different parts of the Commerce area. Keeping the whole project consistent and efficient called for effective communication and coordination. Settling conflicts between teams, spotting project dependencies and adjusting schedules were all part of my everyday work.
The experience taught me not only the technical side of working on the platform, but also how to manage a team and coordinate across many teams. It was a one-of-a-kind, valuable experience that helped me grow both as a team leader and as a professional.
Senior Machine Learning Engineer
What did you learn this year?
I learned plenty of new things this year, but the most impactful was probably that MLOps (Machine Learning Operations) took on a formal shape in my mind, along with its importance when working with ML systems.
Previously, I’d come across loosely defined terms: experiment tracking, model deployment practices, some kind of monitoring and dataset versioning. After a few projects and wider media coverage, though, the whole concept took shape in my mind, and I now understand in depth how to improve or debug the various components and problems of an ML pipeline.
In a Q&A system project, where an LLM bases its knowledge on context built with LangChain, there are many stages where things can go wrong. If we want to debug such a system, merely looking at the final responses won’t tell us much (much like debugging in the software world). Monitoring the deployed model is in fact a key part of MLOps. You have to design mechanisms for monitoring the system’s individual steps (i.e., which documents were selected to build the context for an answer). Only then will you know what to concentrate on first to improve the system.
Software Developer
Meme source
What did you learn this year?
I found out what it’s like to work on a very large-scale project (built on AWS Services) where high availability is the key requirement. An architecture based on a multi-instance setup showed me that problems which initially seem trivial are far from simple once such a design is taken into account. It taught me to get into the details of a problem only after first looking at it from a bird’s eye view.
I also saw that many patterns described in various technical books really do apply in real-life situations, and that this knowledge often proves useful when making critical decisions about a project.
Senior Frontend Engineer
Meme source
What did you learn this year?
This year, I set off on a side quest centred on cybersecurity. I’ve been polishing a range of skills in my spare time. I listen to podcasts - the YouTube channels of David Bombal’s and Network Chuck’s are essential viewing - and I’ve read a few books too, with OccupyTheWeb becoming my favourite author so far. On top of that, I’m going deep into the courses from HackTheBox Academy, which lets me put my newly gained skills to the test on HackTheBox’s broad selection of machines.
I’m not necessarily aiming to become a hacker; I’d rather pay more attention to security, both in my software craftsmanship career and in daily life. This learning path is not only fun for me but also unlike anything I’ve done before - and remarkably mature. I strongly recommend it to everybody, whatever their level of IT experience.
Senior Software Developer
Meme source
What did you learn this year?
Scala programming is mostly what I do for a living. This year, I wanted to try something new, so I began learning Rust. It turned out to be both challenging and inspiring, for many reasons. Some of my Scala skills carried over (such as using function result types to represent errors), while some concepts were entirely new to me (such as ownership and borrowing). It took me some time and practice to feel confident programming in Rust, but so far I love it!
Which programming meme is your favourite? Tell us in the comments!