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)Photo by Nick VN (@_nickvn)
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
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
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
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
Replying to @evanyou
I think at this point we are spoiled for choice - there's a ton of great frontend frameworks now, I'm pretty happy with all the ones I've tried (Vue, React, Svelte mainly). Angular is probably good too, but I don't use it enough to really know much.
1
5
This is how I felt when I found out gitflow is a "legacy Git workflow" that has "fallen in popularity in favor of trunk-based workflows." Atlassian says their gitflow overview is only up for "historical purposes." Thread. atlassian.com/git/tutorials/… #ripvanwinkle @davefarley77
4
22
5
67
Do we really need more swag at tech events? A lot of it eventually becomes plastic waste after years gathering dust on a cluttered shelf. Could be nice for attendees to have options: either get your swag bag or have a donation in your name to an OSS project of your choice.
25
27
4
401
Same experience here: The likelihood of interruption is proportionate to amount of work in progress.
"We have too many meetings and interruptions. We can't get anything done." Naturally. It's all a function of your work-in-progress. "Every work item that has your name attached to it is an invitation to interruption." industriallogic.com/blog/man…
1
1
4
This is a *really* good question for scaled software development.
“How many teams do you need to work with to ship a user-facing feature? At my company, several years ago the number was 1-2. Today it’s often 10-15.” An engineering candidate from a Big Tech company asked me this great question, and it seems like an important metric to track.
4
14
122
Found this via @programmerjoke9; I think it’s brilliant.
44
1,160
86
7,026
How To Measure Software Delivery Using DORA Metrics ➡️ youtu.be/hbeyCECbLhk #SoftwareEngineering #SoftwareDevelopment
2
6
3
33
Rules for playing the long game: Consistency compounds and makes everything easier. Too many heroic efforts also compounds (but in the wrong direction) and makes everything harder. Keep your easy days easy and your hard days hard and just keep going, one brick at a time.
1
21
2
103
There's a thread on HN (not linking to avoid implicit shaming) asking what a company is doing wrong that it can't get sufficient senior engineers to apply to it given that they do no outreach and are effectively average in every way. I recommend not being average in every way.
6
19
9
342
Something every engineer should understand. The code you write should express intent, make your code read like a story. You might have slightly more lines, slightly more typing. But your future self and all your colleagues will thank you for it. Insightful stuff @davefarley77 – at Blackburn, England
1
15
2
39
When teams finally start focusing on solving one problem at a time, it's crazy to witness how fast things start falling into place. We waste our talent by multitasking.
1
3
18
#OAuth, #OIDC, #API #Security. Those topics are the core expertise of @PhilippeDeRyck, who is delivering 2 lectures and a one-day workshop at SecAppDev 2022. We have full course tickets, but also lecture-only/workshop-only tickets. Join us in 3 weeks! buff.ly/3MHLXeC
1
3
On how to be grounded, find meaning, overcome fear of missing out (FOMO), and excel in a dopamine-crazed world:
2
16
1
85
This is the very point I try to clarify here: gtramontina.com/posts/do-rep…. Real vs. accidental duplication.
1
3