My company just migrated our mail servers over to office365. My boss has been excited and could barely contain himself when the migration was done he was having the best day ever after he got a good deal on some new toys...Then I ruined it.

Me (setting up) > WTF!? um...well I guess I don't have email on my phone anymore. These permissions are fucked.
Him > Oh why?
Me > They are ridiculous, I won't give away this much control just to read email.
Him (panicking) > and if buy you a company phone?
Me > Not a fuck it's still a personal device. I'll just sandbox the web version.
Him > Your over reacting, they obviously need them for security blah blah...
Me (sends him the pic) > The minimum system requirement is internet.
(...silence...)

I feel kinda bad for killing his vibe - he's a nice guy and he's only trying to do right by us but now he seems down like his toy isn't shiny anymore because he respects me. I wasn't beating on the stack or his choice (mines running on thunderbird). I just can't support this trend of GOD mode permissions for email / calculator and other single feature apps. I'll use the web app instead. You have to draw the line somewhere...

On the other hand I can't deny that I'm loving the irony that Microsoft just made my life easier and have a deep sense of satisfaction that for the first time ever I got fuck up his Friday :/

I can now leave freely without any regrets!
The slight misgivings I had about leaving this place over the toys they provide, is now gone because I re-realized that while this place adopts new tech, it doesn't adapt to it. So they have shiny tools but the people and processes won't change.
It seems to me that due to pressure to deliver, there is little thought/analysis behind any tech change.

They don't plan to change their wretched delivery pipelines. Everything will be same but on git. So no velocity gains, and same bureaucratic review request process. Such a waste. This attitude applies to their other tools too. They are using a unit test library to write tests that don't use mock. They are using modern languages but without modern idioms. It's like writing C code in C++. And of course theoretically we are agile but actually we're just a waterfall team with managers on our ass everyday and tighter release schedules.

Reminds me of @boombodies recent posts and discussion about business spaghetti reflecting in code.

There are possibly multiple reasons for these problems but I think a large part of it is a lack of empathy/mutual respect. Everyone's too insecure, noone cares for anyone but themselves and people just try to outwit each other.

Devs these days, go all fancy with tech, cutting edge Uber cool shiny toys for designing a system.
Right tool for the right job is a passé. Now, the more you stuff bleeding tech buzz words, the design attracts admiration from bewildered management. [QUOTE] Again, nothing is true, everything is permitted.
Common sense is the craft and simplicity is the soul of efficiency.

When your technical colleagues apply or pressure you to make fixes or implement features w/o understanding how abd why they work. When they discard your proposals/alternatives as inferior, motivating with their superficial knowledge arguments. When they promote new toys over tried and true ones, only because they work using other new technologies and they do stuff automatically, w/o having to think why/how, hoping it'll never fail.

And when it all starts erroring -- turn to @netikras asking to fix the tools I ruled from the beginning as "black boxes of unknown evil"

aren't they the best... :)

is there no longer place for highly technical nerds understanding all the bolts and nuts of big and small tools/systems/solutions..,?

I spent two hours to come up with an algorithm to detect a win and also one to derive the winning indices on any tic tac toe board as long as the size is provided

but i have spent more than twice that same amount of time trying to style component with the shiny toys provided my material ui.

I really just wanted to write less code, but now I have a headache

with my code looking like the death, thanks to the over engineered components provided by material ui

there has to be a way to manage medium to large react codebase

I've googled but everything I see is beginner level stuff, any tips will be appreciated at this moment

Motorcycle owners, riders, I need your advice.

I have my licence for quite a few years now, yet I do not own a steel horse. I keep borrowing one [ninja 650 2010] occasionally for a ~100km ride from someone, 2-4 times per season.

A few weeks ago I did a 1k km mototrip around the country. Gotta say, I loved it! Ever since I cannot stop day dreaming about my own bike.

I'm not an aggressive rider. I like it smooth, steady, comfortable, but with some proper kick occasionally. I'd be riding in a city and taking longer trips [500+km], preferrably with a passenger.

Cruisers are awfully large, city bikes look boring, choppers are loud. Supersports - not my cup of joe. I think I'm settling for the sport-touring class.

Since I don't have lots of xp, it's likely I'll fall, so new and shiny or expensive toys will have to wait.

I feel like falling in love with vfr800 late gen6 [2007-'09], with fine-tuned vtec. I love all the feedback about the steadiness, comfort and power. And it does look cool!

What are your opinions about the vfr? What are the drawbacks?

What other bikes should I look at, that would have similar specs to vfr?

Also, when is it better to buy one? At the end of the season or at the beginning [spring/autumn]?