@NoMad I believe trophy wives opt for a certain style of footwear to increase their (perceived) height.

I am pretty sure the dollar you'd get from each move would be spent on the actual cost of moving.

I suggest a different path to richness.

@Oktokolo Yep, there are so many options. I don't really have a preferred game genre (except rally games on console..), so I wanted to leave it a bit open. Some good suggestions so far, I'll look into them!

@magicMirror not too much I can do about our AWS CI/CD deployment time. But this is not just to fill those minutes, it's nice to have a break now and then too.

Same thing happened to me when I became a millionaire.

Not a true story, I am not a millionaire. But it's the same principle - people have no god damn shame! I had someone contact me out of the blue, asking how things were going just to follow up with "could you go to Facebook and click "like" on a new book that I have published?

I usually scream in silence when my software crashes even here on earth. Inter-planetary deployment won't affect this.

.... and often that's what you have to do.

Similar stupidity: a large institution is unable to attract decent developers because they offer a wage way lower than what any experienced developer can get pretty much anywhere else.

Solution: hire consultants instead, while searching for this unicorn senior dev that will work for peanuts.

It's construction work - you're Bob the Builder without the fancy yellow clothes.

Professional LEGO engineer, where the pieces are code.

Someone had to.

... are they aware of what Excel was designed for? What do they suggest you SHOULD use?

Welcome into the light.

Double oof, it has happened twice.

BUT: I am a firm believer that great execution is more important than great ideas. And since I failed execution I should just shut my mouth and move on.

Storage is cheap.

Streenglo taiped linguishes ar su annojnig!

Documentation:

1. Learn to code.
2. Maintain this shit.

I'll tell you what's worse: you have a really good idea, you create a prototype that a potential client tries out in the real world and tells you they'd be interested in when it reaches commercial quality.

Time goes by, you don't have time to get the prototype production ready and a couple of years later you realised someone else manage to finish a similar product and you know it could have been you.

I hated THAT.

Azure integrates well with anything .NET (obviously..), so if that's your primary framework then the choice is easy. That said, we are a .NET shop running everything in AWS - go figure..

Someone NOT involved in coding made that decision.

@YADU I know what you were trying to say, and I agree. Simple.

I can see why lasers could be a technical challenge, but how about just a repellent that works? The human race with all its achievements is actually unable to figure out something that simply makes an insect go "ahmm... nah, don't like that smell - I'll go somewhere else now".

Take a shower?

Yep, I tried to write my rant in a way not to trigger any discussion about whether React is good or not. I just find it a bit weird that after 20 years in the industry working on a whole array of different technologies this is the first time I can't permanently land on either the "I like it" or the "I hate it" side of one.

Haha, sounds like a place I used to work. And I know people that are still there - what was outdated over 10 years ago when I left is STILL their approach to software development!

Click 'P' -> 5 ms lag -> 'P' show on screen.
Click 'L' -> 5 ms lag -> 'L' show on screen.
Click 'E' -> 5 ms lag -> 'E' show on screen.
Click 'A' -> 5 ms lag -> 'A' show on screen.
Click 'S' -> 5 ms lag -> 'S' show on screen.
Click 'E' -> 5 ms lag -> 'E' show on screen.
Click 'K' -> 5 ms lag -> 'K' show on screen.
Click 'I' -> 5 ms lag -> 'I' show on screen.
Click 'L' -> 5 ms lag -> 'L' show on screen.
Click 'L' -> 5 ms lag -> 'L' show on screen.
Click 'M' -> 5 ms lag -> 'M' show on screen.
Click 'E' -> 5 ms lag -> 'E' show on screen.
Click '!' -> 5 ms lag -> '!' show on screen.

@C0D4 @NoMad

QLD - but not Aussie, just living here, taking your jobs and your women.

..you're aussie I presume?

I don't bother with the built-in user and role management. Too much externally controlled bloat for my DB.

I am a bit wary of using the default setup in large applications because the "one size fits all" illusion is more like "one size fits none - except MVPs and prototypes". Yes, it's very easy to implement third party authentication and you get so much stuff for free right out of the box, but I have yet to encounter a corporate system that doesn't need some customization. And it's easy to just use the bits and pieces you need bare-boned anyway.

My .NET 5 API is pretty much the same as my v3.x which didn't differ that much from v2.x.

What I am doing is pretty simple though, I authenticate and authorize a JWT containing identity info and claims and that's about it.

As always: it depends.

@electrineer

Oops, good point!