just spent twenty minutes debugging why this doesn't work
.something > .stuff:nth-child(0) {
/* ... */
}
can you spot the mistake?
wouldn’t it be nice if something, like, reported an error. or a warning. isn’t this, like, a baseline expectation
C in CSS stands for “the C programming language”
anyway, my gripe here isn’t with css but with Chrome which doesn’t ship a good debugging environment for some relatively basic CSS issues (but it could!)
let’s play a game. you ask me a javascript/programming question (something generic, not “help me with my project”), i try to answer/explain it in a single tweet. let’s go
of course at fb we had a dozen callers to this. some pretty hard to rip out, and it took months of effort to get them locked down and ported to other approaches. no one got fired but it’s nasty when you can’t do internal refactor because somebody added a usage 5 years ago
at one point one of my teammates who is usually very calm and composed deleted some of the internals to “send a message”, which was reverted the next day because it broke a bunch of things for different teams. we didn’t do this again but this started a conversation
we’ve been trying some tweaks to how the information is structured in the react docs beta api reference. would love to hear what you like/dislike about this useState page! beta.reactjs.org/reference/uses…
not gonna lie, i feel pretty lost about the “not api-like” feedback. i’m not sure if this is a slice of power users or representative of what we’ll hear en masse. guess i’ll try to make a dry version to feel it out.
i think the structure of the page is actually very api-like because it’s structured around different overloads and goes outside-in from the api nesting perspective. maybe the headers don’t make it obvious..
sublime text is so good. everyone’s adopting vs code, blablabla, sublime text 4 comes out and quietly fixes a bunch of shit that annoyed me and has better defaults. the only change i do now is .js > open all files as > javascript > jsx. that’s all. a beautiful piece of software.
what’s that? oh it’s just a gorgeous default theme in a minimal, light, friendly editor. nothing to see here
sublime text is a case study in ux design so incredibly well-thought-out that most of us mortals will never — not just approach — *notice* it.
if you scroll down the sidebar to move “open files” out of sight, opening next tabs auto-adjusts sidebar scroll position to avoid jumps
how do you feel about FAQ-like page sections in technical documentation? where the information is laid out as a sequence of question headers and answers instead of a narrative flow
my personal perspective is i dislike faq as a top-level thing but i love it as a leaf thing. like “common questions about %thing%” in the reference documentation page of %thing%. headers make it highly scannable and it models how i’d ask someone instead of reading a manual. ymmv
imo “faq just means gaps elsewhere” is a weak argument. it doesn’t have to be if you close the gaps! then faq serves as a meaningful and rich in information (if it reflects real frequency) index of content elsewhere. it’s a bridge to being a power user. also people don’t read lol
when i was growing up, there was an extremely popular kids book called “harmful tips”. its (joking) premise was that kids always do the opposite of what they’re told, so a book that tells them all the wrong things will surely set the kids on right path.
this one stayed w me:
if you’re biking at the full speed
midway though apartment hallway
and your dad has left the bathroom
and appeared in front of you,
do not turn into the kitchen,
for that fridge is firm and heavy!
better crash into your father,
he is soft. he will forgive.
do not agree with anyone
no matter what the cost,
call out the cowardice in those
who have agreed with you,
then you will earn so much respect
from everyone around,
and you will have so many friends
no matter where you go.