“Product Fail - Silicon Valley Product Group”
“Likewise, we have no idea what it will cost to build. Without knowing the actual solution, this is extremely hard for engineering to predict.”
I’ve been mulling over this post since I read it yesterday. One of the best things I’ve read this month. The agitprop tactics described aren’t exclusive to education.
I can’t be the only one who finds it extremely worrying how eager people are to hand a US company a de facto monopoly over higher education annotations?
A company with a very narrow vision of what annotations should be like to boot?
“My thoughts on Gutenberg Accessibility – Marco’s Accessibility Blog”
“Adactio: Journal—Accessibility on The Session revisited”
Often less is more.
As Craig points out, the Android app ecosystem kind of sucks.
“Software developers should avoid traumatic changes - Drew DeVault’s Blog”
“Making Work Less Stressful and More Engaging for Your Employees”
A benefit of having gotten into web dev via the art, media, and design route is the realisation that if you’d build a new web layout language from scratch, one that adequately serves the needs of designers, you’d end up with something that looked an awful lot like modern CSS
“The epistemology of software quality”
“Studies show that human factors most influence the quality of our work. So why do we put so much stake in technical solutions?”
I mean, I get why Slack rolled out rich text support. I’ve lost that argument at work several times myself. But rich text editing on the web still kind of sucks. It’s very hard to pull off a genuinely nice rich text editing experience. So much can go wrong.
Also, is it just me or has Slack just broken a host of functionality and behaviours with their rollout of a hacky, poorly implemented rich text editor?
You used to be able to write posts in markdown, right? Copy-paste in posts is pretty borked.
I’ve been experimenting with using typescript just to type check JSDoc-style comment annotations and so far it’s been considerably less annoying than going full typescript.
“Michael Tsai - Blog - Full Steam Ahead, But With Feature Flags”
“It sounds like they are still in the denial.”
In case you still don’t believe that Apple’s overall software dev processes are totally messed up.
People keep criticising Safari but...
…it should be noted here that the Safari team is easily the least dysfunctional and most productive software team in Apple’s entire organisation.
Just look at the last four or so iOS and macOS releases, at the various app teams, and contrast those train wrecks with the progress made by Safari during the same period. They’ve been delivering user-facing features and standards-implementations. Maybe not as fast as Chrome but at a steady clip, nonetheless.
Taken in context with Apple’s overall poor software quality, the Safari team looks more like a well-supported flagship team than a team underfunded to the point of sabotage.
“5 Things I’ve Learned in 20 Years of Programming - DaedTech”
You can probably tell a lot about a developer based on which library excites them the most: a fancy graphql client or a fancy hypermedia-oriented client.
I’m firmly in the ‘ooh, hypermedia’ camp 😁