Stop trying to figure out solution Y, when you don’t understand problem X
You’ve had problems with files. Probably due to their file extensions. Let’s say you wanted the last three characters to determine the file type. You ask some people questions about it.
You search for code to find the last three characters. Your coworkers probably have some suggestions, so you ask them as well.
You’re stuck on your solution, without looking back at the problem.
You’ve got into the XY problem. Let’s go into the details of it.
What’s the XY Problem?
The XY problem is asking about your attempted Y solution. You should ask about actual X problem.
Let’s make a general algorithm of the XY problem visible. The definition is from xyproblem.info, so be sure to pay a visit there. …
Legacy code leaves scars for life. Here’s how to avoid it.
How does one deal with legacy code? There is no perfect software system. All software systems have legacy code, and it is our job to mitigate adding more legacy.
“Deadline” developers will implement their changes and leave. Great developers have a broad picture. They incite better understanding and create tools for common features.
One thing you can bring to the project is a shared vision. You need to create an environment where the project will evolve.
Do You Know What Is Event Storming?
Event storming is a rapid, lightweight, and underappreciated group modeling technique that is intense, fun, and useful for accelerating development teams. — Steven A. …
Making software changes is hard. Here’s how to do it
You see a new shiny thing, and you want it. The same behavior happens with software. Every day, we get new libraries and frameworks. Some of those are just hype and have no value to offer your project.
Look at the state of the frontend scene in 2019:
You must be unbiased about dependencies. Ask yourself the following questions:
- What is the purpose of integrating the new library?
- Will it improve performance?
- Will it be a burden for other team members?
I recently had the chance to add phone number masking to a project. …
Don’t Avoid Playing Planning Poker
I read this article about cheating in planning poker. Can’t say I haven’t been cheating a bit.
Do you cheat during your planning poker sessions?
Let’s face it you don’t listen to the whole conversation. Lunch ideas and break time are in your head, and not the bugs.
Scrum master says: “Questions?”, and you’re skimming through the ticket.
Let’s go through why you shouldn’t cheat, and what to do to improve those grooming sessions.
Underestimating Ticket
This happens a lot when someone is not paying attention. He or she picks the common number, without any explanation.
The developer gives a dummy explanation. Compares it to other tickets, or matches to the previous tickets. No ticket is the same as the ones before. …
How to work with Git submodules, hassle-free
Handling a large code base with Git causes a problem with the git fetch command. You don’t need the whole code base to change some styling.
Let’s say you’re building a service-oriented app. Pushing changes to a single repo will cause havoc. Without proper commit messages, you are left with a huge list of unrelated commits.
Committing to separate Git submodules could help. “Submoduling” separates the repo into smaller code bases. Separating concerns will lead to better code organization. For example, one submodule per service would be a good start.
In this article, I’ll try to broaden your knowledge on Git submodules. The article consists of three tips that save my life every day. …
Reading code is just as important as writing it. Here’s how to be a better reader
We’ve all been there: The wrong logic caused a critical bug. You could have prevented it during code review.
Experienced developers know that reading code holds great value. It can reduce how much code you need to write and thus deliver reusable code.
With all that in mind, let’s proceed to the tips I’ve compiled for you.
1. Avoid Working With Code You Don’t Like
I’ve heard that reading open source code will improve my reading skills. I was checking out all the possible projects, but after a while, I got bored.
You may be in the same spot. You can’t read all the code out there.
Be mindful of your time. Not every code you read improves your reading skills. I don’t understand assembly, so naturally, it will bore me. …
Debunking Myths About Closed-Source Software
Working with SAP Hybris or SAP commerce, I am getting a lot of hate about the closed-source software.
Why I chose Hybris over .NET apps?
What about you? Are you a closed-source or open-source developer?
If you chose closed-source, you’re in for a ride. Closed-source has a bad reputation with low flexibility, high specificity, old developers. Does coding closed-source lower your open-source ability?
I am going to debunk some of these myths now!
Why Is Coding Closed Source Hard?
A lot of developers, including myself, think closed source coding is hard.
Take SAP for example and their ABAP language. When I heard of it the first time, I was visibly confused. …
Rant about Java, And Related Tech From Junior Java Developer
Browsing today’s articles you’ll see some on why Java will die. Checking the comments, a lot of readers don’t agree.
Although the 3 billion devices count hasn’t changed, Java won’t go anywhere.
What Got Me Generous Software Development Job Without Perfect Portfolio
You still don’t code for a living. Every developer is saying you should have a portfolio. I am here to say you don’t need it.
You think showcasing your work will get attention. In most scenarios, it can backfire. Every portfolio is pretty much the same, showcase yourself.
I’ve worked both full-time and part-time jobs. I still don’t have a portfolio.
You’ll now discover how to get a job without a portfolio.
Didn’t Someone Suggest You?
One great benefit I got from college is like-minded people. You’ll not only get friends for life but recommendations as well.
Working together on projects will create a greater bond. …
Why you should have a stable personal development journal
Ever worked on something but couldn’t remember what it was? Wished you could reverse time right?
That happens a lot to me. You stumble upon some new ticket that resembles one from before. But you can’t remember.
Well in order for this to not happen, track your days. Not talking about Clockify or Harvest. Your own, simple and stable, personal journal.
Why You Should Use Personal Journal?
You work on a calendar component. Run into an issue with date formatting. Seems like you already had a similar issue. You go back to your journal, search for it. Find related code, apply, issue resolved.
See what you did there? …
