Mastodon Feed: Posts

slightlyoff@toot.cafe ("Alex Russell") wrote:

@NfNitLoop Oh! This is interesting! (and I can't tell you how much of a breath of fresh air typing that is)

SPA might make sense for this! And so might Svelte (which, of all the choices you could have made, is deeply into "least worst" territory).

Can you say more about key management? How does this intersect with Web Crypto? How do you do multi-device?

NfNitLoop ("Cody Casterline 🏳️‍🌈") wrote:

@slightlyoff Ah, yeah. My recent experience has been writing a UI for my “FeoBlog” project. I’m not a UI guy, so looked around at options & landed on Svelte.

The UI is currently an SPA for 2 reasons: 1) the user’s private key should never be sent to the server. 2) proof-of-concept that others can write a standalone client by only using the public API.

In hindsight, wish I’d gone a route that would allow SSR w/ the same codebase. Maybe one day. 😅

slightlyoff@toot.cafe ("Alex Russell") wrote:

Why are people still posting to birdsite?*

*: No, it's fine, I'm familiar with the behavioural economics literature and the many biases and fallacies are self-evident. But thank you. You're here, and I appreciate you for that.

blithe ("Blithe") wrote:

@NfNitLoop I think it counts as a solid because you need to chew it. Both sound great!

slightlyoff@toot.cafe ("Alex Russell") wrote:

@NfNitLoop: *mostly* this means retreating to the server, unless your app/UI features very long sessions behind a login. Happy to discuss your specific situation in DMs.

slightlyoff@toot.cafe ("Alex Russell") wrote:

@NfNitLoop the Svelte ecosystem is wrapped around Rich's (much better) priors and affinities than the React disaster. Prefer that world of those are in a binary choice for you.

All-up, consider the last decade of JS excess as an NTSB crash zone; your job is to map it, understand how products died, and ensure it never happens again.

NfNitLoop ("Cody Casterline 🏳️‍🌈") wrote:

@kornel Yup. I live in a rural area of California that has outages frequently enough that many homes (including mine) have backup generators.

NfNitLoop ("Cody Casterline 🏳️‍🌈") wrote:

@blithe does Mac and cheese count as “solid”? Assuming not, probably a good burger? Thankfully Heiðar makes a kickass burger so I wouldn’t have to go far. 😊

NfNitLoop ("Cody Casterline 🏳️‍🌈") wrote:

@blithe 😬

This was my least favorite part of the subway in NYC.

NfNitLoop ("Cody Casterline 🏳️‍🌈") wrote:

@slightlyoff as a person somewhat recently venturing into JS-web-framework land, I’d love to hear some of the problems here.

I’ve liked using Svelte’s all-in-one (HTML/CSS/code) file structure, and recently saw some CSS-in-JS libraries for React, but haven’t gone far enough down those rabbit holes to experience the pain for myself yet.

Reblogged by kornel ("Kornel"):
computerfact@botsin.space ("Computer Facts") wrote:

Reblogged by cstanhope@social.coop ("Your friendly 'net denizen"):
thezoq2 ("TheZoq2") wrote:

isagalaev ("Ivan Sagalaev :flag_wbw:") wrote:

Apart from being generally educational, this video about human genetic haplogroups will probably be a serious trigger for American white supremacists, who would realize their closest relatives (haplogroup R1) also live in central Africa around Niger and Chad. (Not that I encourage engaging in any sort of meaningful conversation with white supremacists.)

https://www.youtube.com/watch?v=DlQdOUGVdG8

But overall, what a curious mix us humans are!

slightlyoff@toot.cafe ("Alex Russell") wrote:

If the people who were telling you that the last decade's excesses were fine, actually, were out here helping to remediate the damage, that'd be one thing. But that's not where we are.

slightlyoff@toot.cafe ("Alex Russell") wrote:

"Fundamentals don't matter" is how we got "CSS-in-JS".

Groking why holding your platform wrong guarantees a bad time is not an idle skill; it insulates your team from floating dead in the water.

As someone presently digging multiple teams out of the "CSS-in-JS" ditch, with huge wins for products, teams, and users on the other side, I think I've earned this dissent.

Reblogged by slightlyoff@toot.cafe ("Alex Russell"):
chancerydaily@masto.ai ("Chance The Lawyer ⚡︎") wrote:

Attachments:

• 182e142ebc09d5d6.mp4 (remote)

Reblogged by kornel ("Kornel"):
RikerGoogling@botsin.space ("Riker Googling") wrote:

Reblogged by slightlyoff@toot.cafe ("Alex Russell"):
estelle@front-end.social ("Estelle Weyl") wrote:

Reblogged by kornel ("Kornel"):
ds@wetdry.world wrote:

technomancy@icosahedron.website ("tech? no! man, see...") wrote:

facebook, medium, and cloudflare: we're going to join the fediverse!

me:

Attachments:

• Khan Noonien Singh: *big grin* I'd like to cordially invite each and every one of you ... to my block list (remote)

slightlyoff@toot.cafe ("Alex Russell") wrote:

I guess you could say the VCs unbanked themselves.

Reblogged by slightlyoff@toot.cafe ("Alex Russell"):
davidgerard@circumstances.run ("David Gerard") wrote:

Reblogged by slightlyoff@toot.cafe ("Alex Russell"):
froomkin@journa.host ("Dan Froomkin/presswatchers.org") wrote:

Attachments:

• 3714bdea308af507.jpeg (remote)

anathema@girlcock.club wrote:

https://m.youtube.com/watch?v=CSJXle3LP_Q

Reblogged by slightlyoff@toot.cafe ("Alex Russell"):
maxkennerly@mstdn.social ("Max Kennerly") wrote:

Attachments:

• Elizabeth Warren: I Fucking Told You This Would Happen (of course this is just a joke, that's not the real title) (remote)

slightlyoff@toot.cafe ("Alex Russell") wrote:

An important addendum to this (while I wait for another build to finish) is that the goal of getting in touch with these other sub-disciplines is to help you identify which skills *in your own layer* are foundational, and which are less likely to survive the next correction.

Gaining an appreciation of the stack from the point of view of other layers will help you gain perspective on your own systems, which makes you more valuable and effective.

slightlyoff@toot.cafe ("Alex Russell") wrote:

No, you don't have to do VHDL, or etch chips, or rebuild a core router from the OS up, or crimp your own cables -- at least not if you don't want to. But if you work in browsers, you'll need to learn OSes and something about web development.

If you work on the web, you'll need to learn a lot about browsers and something about what designers are struggling with.

And if you're a designer, you'll need to learn about your medium (web development) and content design.

slightlyoff@toot.cafe ("Alex Russell") wrote:

Now, we all operate in different levels of the stack more-or-less, and a constant truth is that there will always be a higher and a lower level adjacent to what you are comfortable with. That's OK! It's natural. Don't let it get you down.

But also don't let it become a crutch. It's *necessary* to begin to grow an appreciation and understanding of the terms of debate in those layers as you progress. They're not "your" layer? OK. Cool. But you must become conversant in 1-2 above/below.

slightlyoff@toot.cafe ("Alex Russell") wrote:

The way this plays out over a career is subtle but powerful. When those around you understand you to be a lightweight, or to "only know X", it will eventually cause them to refer you for fewer positions. Doors will remain closed that you might not even perceive. In moments of change, peers will not look to you for guidance.

All of that adds up.

slightlyoff@toot.cafe ("Alex Russell") wrote:

For my crimes (looking at LinkedIn...yes, I know), a point I cannot stress enough for those who MSFT refers to as "early in career":

Learning the trendy thing without developing a parallel skill in the fundamentals will *always* catch up with you. Every time.

You *do* need to understand the platform below you.

Really.

*Really* really.