43 pages tagged with "software"
This is a question that I have encountered with some frequency for a long time. So I thought I would put together my thoughts on the subject here.
This will be controversial, but let’s talk about the QA position. The hidden truth behind the lack of software quality and why this should concern you if you write software.
To introduce a new tech stack for the entire team, it’s important to bring “why?” and a strategy to make it happen among the team because it will affect everyone.
Talking to a friend about agile, he asked me a fascinating question remarking how badly sometimes Agile and Scrum fit together, especially regarding meetings. These are my thoughts about this topic.
Let’s assume you already know what the agile manifesto is. Let’s consider that you apply most of the “extreme programming” values, principles, and practices. How can you work with other teams that aren’t agile?
I recently got a great question on Twitter which got me thinking for a while and I decided to share my thoughts about it.
We all have been junior developers at some point. This is easy to know because it is at the very beginning of your carrier. Your responsibilities were narrowed down by other peers who were looking after you.
There are two known schools in TDD: the mockist school (aka Outside-in) and the classicist school (aka Inside-out).
These are two different techniques. The key to each of them is about the mindset and context of what you want to achieve.
The complexity here is not about writing tests itself, but the habits that we have to change to create software that is easy to be tested.
The Trident Career Model by Patrick Kua has three tracks. Each track represents where people spend most of their time or energy.
A great compilation of all topics that are important for management: 1:1s, performance reviews, hiring and laying off, workplace politics, remote work, and others.
The book is divided into 3 parts: the first part covers things a new manager should know, the second and third parts go into topics that all managers should master.
What is Open-Source Software (OSS)? What are their benefits? How can you start contributing to any OSS? Pet projects? Knowledge sharing? Why all of these?
The new Functional Programming language build-in PHP. Check it out!
Mocking is useful, but “what to mock” usually turns out to be a bit more complicated than expected if you don’t treat this carefully.
Discover another way of sharing suggestions with your development team.
Using array_merge inside a loop is a performance killer. The spread operator will help you to improve this by flatting the array.
Argument unpacking, function variable argument list, and variadics function.
Objects are the central concept of languages like Java, Python, C#. Applying best practices for object design means that your code will be easy to read, write, and maintain.
This book captures dozens of techniques for creating pro-quality OO code that can stand the test of time.
Domain-Driven Design Distilled brings DDD to life. Whether you’re a developer, consultant, or customer, it will help you understand it, so you can benefit from its power.
These tests are also known as Characterization tests.
This book helps you get your web applications back in shape. It contains many techniques for decoupling from infrastructure (like the framework or the database).
“The best guide that brings your coding and architecture skills a level up. All the modern PHP features combined with the elegance of a well-designed modular design.”
In December 2015, PHP 7 introduced scalar type declarations and with it the strict types flag. What is this new feature?
If you see something, in the scope of your current task, that can be easily improved, improve it. And if you have any questions about it, ask.
Why you should consider testing as part of your daily development habit and how it’s directly linked to the software quality.
Programmers who endure and succeed amidst swirling uncertainty and nonstop pressure share a common attribute: They care deeply about the practice of creating software. They treat it as a craft. They are professionals.
Tap into the wisdom of experts to learn what every programmer should know, no matter what language you use. With the 97 short and extremely useful tips for programmers in this book, you’ll expand your skills by adopting new approaches to old problems, learning appropriate best practices, and honing your craft through sound advice.
Even bad code can function. But if code isn’t clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn’t have to be that way.