327 karma · joined December 15, 2017
I think you can substitute Blazor with a large number of frameworks (RoR, Meteor, django, etc) and find a lot of people who believe it is the future of developing SPAs.
that said, i take exception with these claims that the user is “an idiot”. it comes off as arrogant to me.
what is the competing tech?
i never type with capslock on, and find using it for escape helps my vim workflow
i even still buy the occasional booster pack.
for a while i was very much into ebooks for many of the reasons others on this thread have sited, but eventually started purchasing physical copies again. part of this was uncovering a well-worn copy of Dune in a box. it was printed sometime in the early 1970's and everything from the cracked spine to the yellowed pages to the "sale, 10¢" written in a flowing script the inside cover brings a nostalgic value i couldnt possible replicate with an ebook (for painfully obvious reasons). furthermore, on uncovering this book i found the bookmark to be the receipt from the bookstore that i purchased it from a decade ago. other books on my shelf contain similar personal items such as a postcard welcoming my daughter to kindergarten, a $1 silver certificate i found in my change years ago, a receipt from a store that i used to frequent as a teenager whose proprietor has since passed away...
[edit]: correcting a typo
https://github.com/flexport/latitude/blob/master/Text.jsx#L6... https://www.flexport.com/design/components/Text
#neverforget
from the perspective of managing technical teams i've only found the "manager's schedule" (as described) to be a bother to _me_ and _my_ time management. this has been a major pain in the ass when i had to kick out feature work and caused me to spend several super late nights to wrap things up. this didn't affect my team directly; no doubt my exhaustion impacted my mood and thus my interactions. not sure if i was a total dick (never got that kinda feedback, direct or indirect...but how knows...), but i certainly more than once had the posture of defeat as i shuffled from a pairing session to a strategy meeting.
i tried my hardest to create a big sandbox the devs could own and (mostly) self organize. with the help of sympathetic product managers we switched from scrum to kanban and dropped physical standups (and their associated shitty conference call experience) for a dedicated slack channel. we leaned heavily on tech and a couple basic asks such as "try to post status around the same time every day", "important communication goes in email, not in slack", "if you know your schedule, add it to the team calendar" and so on. it was not perfect but it worked out...for the that team, project and business conditions.
now, i have also certainly (and most commonly) experienced shitty remote situations where people on the speakerphone are forgotten, work from home is viewed as a negative and local time is gravely disrespected.
obviously i don't know much about this area...if anyone has canonical references they could point to i'd love to learn more.