Nick VN (@_nickvn) header
Nick VN (@_nickvn) profile picture

Software engineer. Solves business problems by building software 👨‍💻. Always balancing best practices, pragmatism and creativity.

Ghent Area, Belgium
Joined January 2013
Photo by Nick VN (@_nickvn)Photo by Nick VN (@_nickvn)
🎉🎉🎉 v1.0.0! @nvnh/clock is a small library without dependencies for mocking time in #javascript. npmjs.com/package/@nvnh/cloc… After using it for a while in production, a few bug fixes and usability improvements, it was time to make it official.
1
39
Just converted my website from Wordpress to @astrodotbuild and now I wish I did it sooner 😅 It's much more lightweight, much easier to host and to my surprise, it didn't take a lot of time. nvnh.io
2
5
364
Failing test, check! Time for lunch.
Ending your day with a new failing test is leaving a puzzle for you to solve the next day.
30
Just published a Javascript package called @nvnh/clock, a small library without dependencies for mocking time in Javascript: npmjs.com/package/@nvnh/cloc… It's inspired by this clock package for Go I really liked working with: pkg.go.dev/github.com/facebo…
1
1
104
If you feel like your diagram is getting too complicated, you're either trying to communicate too much in 1 diagram, or the problem is not with your diagram, but with an overcomplicated architecture.
36
Great points by @davefarley77 and @tdpauw . "Code reviews are not there to catch bugs." They're there to catch low quality code. New low quality code does not necessarily have more bugs. The real problems start when you start building on low quality code.
1
3
12
3,560
High growth rates (in an industry, community, startup, etc) mean you have a lot of newbies; having a lot of newbies (persistently) means you have high growth rates. One of these intuitions which people get repeatedly surprised about, so, mentioning it out loud.
9
20
3
206
60,823
A suggestion: If your dev team does great work, find ways to tell the rest of the biz, in ways that they will understand and appreciate. Try and do this without talking about the technology!
3
12
1
63
7,733
That's a good point and the reason I included "Make an effort to understand legacy code" in "3 underrated things great developers do" nvnh.io/index.php/2022/11/28…
When something isn't obvious, people may declare it complex. "If I don't immediately understand it, as smart as I am, it must be because it's too convoluted. That's the only possibility." Anything unfamiliar is declared "complex."
2
1
7
2,305
This! I once had a discussion about the need for reactive streaming for our backend-frontend communication. If we need reactive streaming to the browser, we have a design problem. We don't need to throw on complicated tech, we need to change the design.
Sometimes, a performance problem is actually a design problem. Example: “How do we fix the performance of this page showing 1,000+ items?" Answer: Stop showing so much stuff at once. What user can absorb 1,000’s of items? Make it easy for the user to find what they need.
28
Kubernetes, Event Sourcing, Chaos Engineering, ... People are attracted to sexy, complex-sounding things because it's cool to talk about them, and they can act like it will fix all of their problems. So let's talk about underrated things developers do: nvnh.io/index.php/2022/11/28…
2
Replying to @BryanFinster
In an industry that is constantly doubling in size, half of the people (or more) will always be newbies. Dunning-Kruger tells us that those people think they know more than they actually do. So no, we will never overcome the knowledge debt.
1
2
8
Nick VN retweeted
Exactly this! Also, techniques for loose coupling applied on an implementation doesn't imply a loose coupling of the domain. If the domain doesn't support loose coupling along the same lines, complexity explodes.
1
1
1
6
For everyone wondering if writing tests is a waste of time, think about all the time you spend testing manually: restarting your application, getting it in the right state to test, do the actual test, see that it's not working yet, make some changes to the code, repeat...
1
Write tests where you want your module boundaries to be. Writing them any other place just shifts the boundary — and your modularization.
6
97
10
468
In production, we often use a reverse proxy to handle HTTPS for us, so why wouldn't we do it on our development machines as well? nvnh.io/index.php/2022/10/24…
Very similar to my experience: learned to code as a hobby, making games and graphics software, learning how things work, solving problems for people with code that clearly expresses ideas and how it works. Software Engineering❤️
Things I love about writing code - a thread... 1/9
Don’t get caught up by test categorization—it doesn’t matter whether you’re writing unit tests, integration tests, or whatever else. What matters: 1. Your tests assert cases like a user 2. Your tests are deterministic 3. Your tests are unequivocally labeled
7
29
2
172
Feeling uncomfortable with the magic of mocking modules? You can avoid it using dependency injection! nvnh.io/index.php/2022/09/18…