Security, Systems & Network Automation| Jakub Jarosz
"I have two news for you, bad and worse," said the mechanic. "The battery is dead and I won't get a new one until Monday. Forget about your annual inspection today," he continued. "But..." you started. "There is no but." he cut short. No setup, no testing. Just like in your Go program.| Jakub Jarosz
In Go, we build packages - fundamental Lego-like blocks that we assemble in modules and use to build applications. That's why it's crucial we start designing packages by modelling their public APIs. Let's roll up our sleeves, sharpen the scalpel and start the second code surgery. This time, we focus on tests.| Jakub Jarosz
This week we do small refactoring to illustrate how we can improve code readability and reduce cognitive load.| Jakub Jarosz
For us Go developers, writing less code means fewer opportunities to make mistakes. But how about achieving more by doing less? That sounds appealing. Isn’t it? And how about spending less time writing code to force the compiler not to optimise the benchmarking functions?| Jakub Jarosz
Security, Systems & Network Automation| Jakub Jarosz
Security, Systems & Network Automation| Jakub Jarosz
How do you know if what you are building is the right thing? How do you know if the product you just put into customers' hands doesn't harm them? Don't put them into hospital or worse, kill them?| Jakub Jarosz
In this article, we clarify the Golang security patching cycle. You'll learn how to identify vulnerabilities in your Go code and Go binaries and gain the insight needed to assess if these issues impact your application and pose security risks.| Jakub Jarosz
How should I organize my Go code? What directories to create? How many nesed levels? Where to put what files? How about tests and test data? Shall I follow this and that template? Could we automate project structure generation?| Jakub Jarosz
Security, Systems & Network Automation| Jakub Jarosz
You pushed a small change to the Kubernetes cluster. It broke the production environment. You became famous in your company, but you quickly fixed the issue. Now it's time to analyse the root cause! Welcome to the post-mortem!| Jakub Jarosz