Sleek v2.0 public release is here
Lorem ipsum dolor sit amet, consectetur adipiscing elit lobortis arcu enim urna adipiscing praesent velit viverra sit semper lorem eu cursus vel hendrerit elementum morbi curabitur etiam nibh justo, lorem aliquet donec sed sit mi at ante massa mattis.
- Neque sodales ut etiam sit amet nisl purus non tellus orci ac auctor
- Adipiscing elit ut aliquam purus sit amet viverra suspendisse potent i
- Mauris commodo quis imperdiet massa tincidunt nunc pulvinar
- Adipiscing elit ut aliquam purus sit amet viverra suspendisse potenti
What has changed in our latest release?
Lorem ipsum dolor sit amet, consectetur adipiscing elit ut aliquam, purus sit amet luctus venenatis, lectus magna fringilla urna, porttitor rhoncus dolor purus non enim praesent elementum facilisis leo, vel fringilla est ullamcorper eget nulla facilisi etiam dignissim diam quis enim lobortis scelerisque fermentum dui faucibus in ornare quam viverra orci sagittis eu volutpat odio facilisis mauris sit amet massa vitae tortor condimentum lacinia quis vel eros donec ac odio tempor orci dapibus ultrices in iaculis nunc sed augue lacus
All new features available for all public channel users
At risus viverra adipiscing at in tellus integer feugiat nisl pretium fusce id velit ut tortor sagittis orci a scelerisque purus semper eget at lectus urna duis convallis. porta nibh venenatis cras sed felis eget neque laoreet libero id faucibus nisl donec pretium vulputate sapien nec sagittis aliquam nunc lobortis mattis aliquam faucibus purus in.
- Neque sodales ut etiam sit amet nisl purus non tellus orci ac auctor
- Adipiscing elit ut aliquam purus sit amet viverra suspendisse potenti
- Mauris commodo quis imperdiet massa tincidunt nunc pulvinar
- Adipiscing elit ut aliquam purus sit amet viverra suspendisse potenti
Coding collaboration with over 200 users at once
Nisi quis eleifend quam adipiscing vitae aliquet bibendum enim facilisis gravida neque. Velit euismod in pellentesque massa placerat volutpat lacus laoreet non curabitur gravida odio aenean sed adipiscing diam donec adipiscing tristique risus. amet est placerat in egestas erat imperdiet sed euismod nisi.
“Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum”
Real-time code save every 0.1 seconds
Eget lorem dolor sed viverra ipsum nunc aliquet bibendum felis donec et odio pellentesque diam volutpat commodo sed egestas aliquam sem fringilla ut morbi tincidunt augue interdum velit euismod eu tincidunt tortor aliquam nulla facilisi aenean sed adipiscing diam donec adipiscing ut lectus arcu bibendum at varius vel pharetra nibh venenatis cras sed felis eget dolor cosnectur drolo.
Photo by Joey Nicotra on Unsplash
First let’s understand why we’re talking specifically about debugging.
The 3D Process
Design
Develop
Debug
Looking at those 3 parts, the most important part to improve, in my viewpoint, is debugging your code.
Why?
Because Design can happen and can also not happen. It can also be a short or a long process. It’s under our control.
Development has to happen anyway otherwise there’s nothing to debug.
But debugging WILL happen, and it will undoubtedly occur near the end, when the deadline is close (or the night gets short), when stakeholders are pushing, and when your creative energy is usually depleted.
While technical Design is pure creation – you’re just imagining up your code architecture and actually creating it in your head / whiteboard, and Development is the physical creation, which has its struggles but is still always going forward (as you create more and more components of your app), debugging just doesn’t feel like creation, but more like fixing what’s already working (or mostly working).
So what can we do to alleviate this part of the process which is the most undesirable, painful and feels the least under our control? What superpower will mostly help us tackle this part and bring those hard-to-find bugs to their knees as fast as we can?
Logic
As opposed to Design & Development, where imagination and creativity are key, debugging is much more of a straightforward machinery process. Which means it can get boring fast, but if we look at it as a game of beating those red-eyeing bugs, we can think of it in terms of winning those bastards and sending them straight to outer space using our (re)discovered superpower, logic. Specifically, solving any bug will consist of:
- Make sure you understand what the issue is.
- Ask for any missing data / reproduction steps.
- Fire up your application and get your starting point right.
- Make sure it still reproduces.
- Break down the flow down to pieces.
- Take a look at each piece separately and document its results.
- Concentrate on the first piece that seems broken.
- Find the solution for it (it could be in yours or someone else’s code).
- Get it fixed and move to the next one that seems broken.
- Repeat steps 7-9 until morning (or until bug is solved).
The key takeaway here is point #5. Obviously to do it right you have to go through the other points first. But point #5 is the one which makes the bug / flow manageable and something that you can put under control. That would be the key point – control the bug, because if it was under control in the first place, it wouldn’t have been a bug 🙂
So next time you’re close to your deadline and you’re watching the list of bugs on your issues management system piling up, focus on your mind’s superpower and start blasting those bugs away!
Cheers
Nadav
Nadav Lebovitch
Nadav Lebovitch is the Founder & CTO of nSoft, helping VC-backed startups build scalable web and mobile solutions. With 18+ years of experience, he has led hundreds of projects using modern technologies like React, Node.js, and PostgreSQL.
