@mjovanovictech Whilst simplest to implement, note that url versioning forces upgrades on ALL clients, even if they don’t use the endpoints you changed, as it is a branch in the entire api. Header and query string methods allow you to version individual endpoints minimising disruption to clients
@blaken@mjovanovictech If you want to share between solutions and they have the same arch constraints then great. If you want a low barrier to entry option that doesn’t require learning Roslyn, this is a great alternative. We solved all our arch constraint enforcement issues overnight.
@blaken@mjovanovictech Analysers can give you more responsive feedback, but the barrier to entry not just for you but your devs to contribute is far lower. Analysers also impactful on solution perf on very large solutions. This moves it out to test time in those cases.
The way that Jensen Huang runs Nvidia is wild:
40 direct reports, no 1:1s
- Believes that the flattest org is the most empowering one, and that starts with the top layer
- Does not conduct 1:1s - everything happens in a group setting
- Does not give career advice - "None of my management team is coming to me for career advice - they already made it, they're doing great"
No status reports, instead he "stochastically samples the system"
- Doesn't use status updates because he believes they are too refined by the time they get to him. They are not ground truth anymore.
- Instead, anyone in the company can email him their "top five things" with whatever is top of mind, and he will read it
- Estimates he reads 100 of these everyone morning
Everyone has all the context, all the time
- No meetings with just VPs or just Directors - anyone can join and contribute
- "If you have a strategic direction, why tell just one person?"
- "If there is something I don't like, I just say it publicly"
- "I do a lot of reasoning out loud"
No formal planning cycles
- No 5 year plan, no 1 year plan
- Always re-evaluating based on changing business and market conditions (helpful when AI is developing at the pace that it is)
This org is optimized for (1) attracting amazing people, (2) keeping the team as small as it can be, and (3) allowing information to travel as quickly as possible
@mjovanovictech Sync communication between modules introduces coupling, so tend to avoid. However that can sometimes cause challenges if you need to rely on some other module for immediate end user feedback.
In .NET 8 it finally feels like we cracked the “full stack” nut with Blazor. The recent move of many JavaScript client side frameworks to server rendering have given blazor a real shot at existing amongst these giants. #dotnet#blazor
https://t.co/JXfrTTjOtn