Over 4 years ago our CTO wrote a blog post claiming that technical debt is the number one reason why software development projects get derailed. Years have passed since, and I can say that he couldn't be more right. Although I see that business owners get more familiar with the term technical debt, it quite often plays the role of an elephant in the room. And in the long run, such stories rarely have happy endings. So if you don’t know what the technical debt is, or you do but you don’t think you should worry about this villain - better read further.
Posts tagged "software-development"
Not everyone was a scout in his youth. Most of programmers, however, have probably heard of the Boy Scout Rule in software development. But can you name a few of the activities that are part of that rule? When I started to explore this topic, looking for what exactly needs to be done to say "I just applied the boy scout rule", I only found one thing: "Leave your code better than you found it" - everyone quotes Uncle Bob. But what does it mean? What am I supposed to do exactly?
I love speed. Users demand speed. Check out how I increased page speed from 7.6 sec to 1.23 sec within a couple of minutes and to 0.6 in 4 hours of developing time. I did it without knowing much about business logic…
While looking for inspiration to write this post, I ran into a help request on a popular PHP community forum. When he showed some snippets of code, the problem became obvious. Some time ago, I had a similar situation...
I want to present you a real story that happened in a project we took over. On this day, Sentry revealed a strange error. The short analysis showed that the error occurred when a user was removed. But wait, there is no such feature as removing a user! What happened?!? I analyzed the logs and found out that someone wanted to delete his/her profile picture and instead... removed himself!
== or ===? How many equal signs to put up so that it is correct and that nobody in the code review has a problem with it? Why is it so tricky in PHP?
Task completion reporting may not be the most interesting part of the software development process, but when it’s done right it can be both effective and effortless, significantly speeding up internal testing and customer acceptance. Good reporting ensures that everyone is on the same page, minimizes guesswork, and allows you to identify potential misunderstandings. It also helps to make sure that work reported as finished is actually done. In the end, it contributes to speeding up the development process and shortening time to market for new features. To make it happen, I suggest introducing 6 simple rules of good task completion reporting.
When building an application, you will for sure reach a moment when someone suggests you do a full rewrite. This could be your developer or anyone else (including yourself). This scenario might be tempting as, in most cases, the software you have is not ideal. It has bugs, breaks from time to time, doesn’t scale well, the code is ugly, the framework you use is not maintained anymore, etc. It might feel a bit like wading through a vat of molasses. You feel like this is the best solution to all your problems, maybe you can already see the shiny new application that you are going to build and the money it will earn, happy customers, no bugs, etc.
PHP7.2 was signed as RC6 in 09 Nov 2017 and GA released in Nov 30th's. In Accesto we try our best to keep updated with all new features and changes. Here is a list of the most important things you must know about the new release.
In September we are celebrating the birthday of Accesto, this year we will turn 7. For me it's a double anniversary because a year ago in September I joined the team. Using this opportunity, I would like to summarize this period as well as show how our work looks like from the inside.