.Net Developer; fan of domain driven design; enjoy making things easier for fellow devs

Joined January 2010
6 Photos and videos
Dave van Herten retweeted
23 Sep 2020
Basic, but important: Product teams should rarely prioritize Efficiency higher than Effectiveness. And yet so many do How to tell them apart: Teams that value Efficiency obsess over Speed & Process Teams that value Effectiveness obsess over Customer Problems & Differentiation
22
120
866
Dave van Herten retweeted
4 Mar 2020
How to build a remote company: - look for people great people, anywhere - pay them through @remote - meetings with @zoom_us - write stuff down, all the time in @NotionHQ - put your code in @gitlab - get together if you can, don't work when you do - have calls just for fun
33
129
707
Dave van Herten retweeted
We released patch 1.2 of #TheOuterWorlds today, and it includes a fix for the dreaded "the game thinks my companions are dead" bug, which I believe I spent more time investigating than I have for any other individual bug in my career (1/18)
220
4,966
17,049
Dave van Herten retweeted
29 Jan 2020
Tip: @ChromeDevTools has a Shadow Editor built in!
65
1,725
6,399
Dave van Herten retweeted
🚨 πŸ“£ Announcing: πŸ†πŸ”₯πŸ†πŸ”₯πŸ†πŸ”₯πŸ†πŸ”₯πŸ†πŸ”₯πŸ† πŸ”₯πŸ† TestingJavaScript.com πŸ†πŸ”₯ πŸ†πŸ”₯πŸ†πŸ”₯πŸ†πŸ”₯πŸ†πŸ”₯πŸ†πŸ”₯πŸ† πŸ’Έ There's a HUGE discount right now too πŸ’Έ From total beginner to EXPERT tester with 8.5 hours of *super* high value-to-minute content (I don't waste your time), and ... 1/9
38
237
710
Dave van Herten retweeted
not using a framework is sometimes creating an ad-hoc, undocumented, non-standard, can't look up answers on stackoverflow, bespoke personal framework
4
23
155
Dave van Herten retweeted
10 Sep 2019
Most common mistake software developers make: putting stuff in the wrong place. Coupling responsibilities and concepts that should be kept separate. For me, this is 95% of software development. Just figuring out *where* things belong.
22
134
633
Dave van Herten retweeted
19 Aug 2019
One of the most valuable concepts I learned in school: Opportunity cost - The loss of potential gain from other options when an option is chosen. This is why getting comfortable with saying "no" is important. Every "yes" is an implicit "no" to something else.
6
17
131
Dave van Herten retweeted
Today is YC's Demo Day, where founders try their hardest to give away control of their company. Let's celebrate bootstrapped and self-funded founders with our own "Demo Day". Reply with: 1. A description of your company in 10 words or less 2. MRR (if any) 3. Link to your site
344
310
1,632
Dave van Herten retweeted
The longer I do design systems the more I feel like seeing a lot very flexible APIs in your tools is a red flag. It's another thing in Decision Debt land. Thread:
18
132
583
Dave van Herten retweeted
Whenever a rule is added in a team, first ask: Will the existence of this rule discourage future people from using their human judgement to make smart decisions in nuanced situations?
9
141
599
Dave van Herten retweeted
Optimist - The glass is half full. Pessimist - The glass is half empty. Developer - The glass is twice as big as it needs to be. Product Owner - We need to put 3 times more water in that glass; Make it happen
11
48
144
Dave van Herten retweeted
The most frustrating thing in debugging is not finding the problem. It's when you find the problem, see the problem, fully understand and agree with the problem...and now don't understand how it EVER worked.
7
53
341
Dave van Herten retweeted
What good is a retro if you cannot actually implement improvements? In that situation, a retro is a demoralizing exercise in futility, and the SM needs to improve the surrounding org, as per the Scrum Guide, to get the team motivated.
10
25
117
Well that was accurate.
What UI wizardry is this??
Just saw this section in the amazing Pair Programming documentation from @PairWithTuple. I believe this to be good advice for development in general, not just pairing!
2
2
Dave van Herten retweeted
For those of you who hate microservices because of some maintenance or testing nightmare, there is such a thing as bad design/implementation. Simply using an architecture does not guarantee a good (maintainable, testable) system. That requires knowledge, experience, thinking, &c.
5
50
157
Dave van Herten retweeted
10 May 2019
Most advice is too general, hence, it might apply to you, or not. That’s not a good reason to discount it though. You should evaluate advice to uncover its intended audience and any implicit prerequisites.
1
1
1
Dave van Herten retweeted
I had never seen this expressed in art before but brilliant!
28
3,520
11,819