Don’t lead by example The title is a little misleading, it’s not that you shouldn’t lead by example. It’s that you need to chill out, set expectations, and be a part of the team. This article is a good read based on an engineer’s experience as a tech lead at Dropbox. Digging into Postgres’s Lesser Known Features Depending on your use-case you may not need to add Redis or Elasticsearch to your application if you are already using Postgres.
Hacktoberfest presented by DigitalOcean and DEV Hacktoberfest is here! Contribute to the open-source community during the month of October and receive a free t-shirt and stickers! Role Base Access Control (RBAC) Design For Microservices This article provides a brief overview of how one might implement role-based access control in a microservices application, including a diagram of the architecture and the data model. It’s not an in-depth article and encourages further investigation elsewhere, but it’s a nice introduction with some helpful tidbits.
Don’t get locked up into avoiding lock-in If I had to select a single article to send out, it would be this one. A lot of people get worked up over avoiding vendor lock-in, but lock-in isn’t a black-and-white issue. It’s full of shades of grey and this article sorts through those shades, names them, and offers a strategy forward. An Internal PaaS to Manage AWS: Don’t Do It! Atlassian built an internal system that they have placed in front of AWS to regulate access and to help aid in application deployment.
Jakarta EE 8: The new era of Java EE explained - Red Hat Developer I’ve always been a bit fuzzy on the alphabet soup that is Java, but I’m finally starting to get that all sorted out in my head. Java EE, now Jakarta EE, has gone open source. Jakarta EE 8 is a set of specifications extending Java SE, another set of specifications. With this change, some licensing issues are being cleared up and Java is working to positional itself for the cloud.
Composing better emails No matter how much you like your chat application, you probably are still sending a lot of emails. Take the time and learn to email well. This article has some common recommendations that can speed up understanding of a communication and make people’s job easier. Deconstructing the Monolith Just because microservices are popular doesn’t mean they are the right answer for everything. Shopify was, for a long time, a single Ruby on Rails monolith.
Get your work recognized: write a brag document Have you ever been asked for a list of what all you accomplished in a given time period and drawn a blank? I can barely remember what I did last sprint, let alone 6 months ago. Keep a document that includes what you have done. It can be a short blurb about it, enough for you to fill in later, or it can be a whole explanation of the situation around the work.
Two Good Practices Agile Says You Don’t Need - DZone Agile There isn’t much consistency in Agile, just the principals. Beyond that, it is the wild west. That’s part of the strength of it but also part of the weakness, it leads to a lot of misunderstandings. I’ve never seen Agile done the same way twice. This article focuses on two things that many people involved with Agile say you don’t need or shouldn’t have: specialists and initial planning.
Why We Need To Talk About Burnout In The Tech Industry Burnout seems to be a common thing in the technology industry, but that isn’t healthy. This article includes some things that can be done to combat burnout and what the symptoms are. Managers and contributors alike need to be mindful of these things, but ultimately you need to take care of yourself. Stay healthy. Experts Attempt to Explain DevOps–and Almost Succeed | Linux Journal
Creating a Code Review Culture, Part 1: Organizations and Authors Creating a Code Review Culture, Part 2: Code Reviewers Code review is something I am very passionate about. This article walks through the parts of a culture that fully supports code review to its fullest. I wish I could say I had been involved in a code review culture this thought out, but I can’t. I’ve been involved in teams that have put a strong emphasis on code review and ones where it wasn’t as strong.