A question came into focus for me yesterday: is the success of Open Source for early-in-career folks building portfolios a contributor to frontend's ethical dessication?
OSS is "software for me, incidentally for thee"; does introducing that ethos to young programmers keep us from driving home the lesson that when you get paid to write code, your responsibilities are to users and customers?
Yesterday we had another example of LLMs creating support issues for us.
User: "hi, how do I do this thing? Your docs say I can go here and change some options, but there's no settings there"
Me: "that's right, we don't have such a feature, but also we don't say you can do it in the docs, where did you read that?"
User: "oh I didn't actually read the docs, I asked 'AI' and it hallucinated this answer. Sorry!"
At this rate I'm looking forward to 2025 when I'll be spending 100% of my time doing support to correct falsehoods about our app made up by LLMs
The frontend community is in crisis. I know, because I could spend every waking hour helping e-commerce and productivity apps fix the *unbelievably* bad performance that is now the hallmark of contemporary, JavaScript-first web development.
But it's worse than that. This stuff has infected public services; the sorts of sites that have to serve *everyone*, iPhone or no.
Part 2 of this series is the hardest to watch, but essential to understand how far we've fallen:
I know that there are complicated economic theories about what determines inflation and wealth and such, and that particularly capitalists love claiming that it's a really complex system, but every time I've looked into that supposed complexity, almost all of it was just proxy metrics for something really simple.
So... is inflation actually influenced by anything *other than* the relation between 'amount of money in the economy' and 'change in wealth inequality'? Or is it just all smoke and mirrors again?
(Please do not repeat economics textbooks at me, I'm looking for a well-reasoned answer that approaches the topic critically, not "everybody knows that..." type answers)
Death mention. Tech industry. callous metaphors.
Anyway, think about the implications of the things you say.
I listened to people talk about what this company would do with this man inevitably died for years. I probably repeated the line.
Everyone always said it with a kind of chuckle. As if it was easier to say that than "retires" or "takes another job." As if it was somehow better to imagine his children grieving than it was to suppose he'd ever just move on.
Death mention. Tech industry. callous metaphors.
I spent half a decade working for a big tech company in the Games/Social space. You've heard of it, but I'm not naming it here because the point of this story is universally applicable.
One of my key job responsibilities when I was brought on was Learn Everything from That Guy so someone knows what he knows in case he gets hit by a bus.
Eventually, I built a whole team to operate the tools That Guy built, and to build new tools that solve the same problems in our new software stack/with less manual work.
That Guy grew less vital to the success of the company, and he retired shortly after I left. Everything he had been responsible for was transfered to two people I hired and trained, or was turned off.
Less than a year later, That Guy was involved in a head on collision and died on the spot. This was a few days ago. I don't know if the collision involved a bus.
The pragmatist in my head says "see, it was a real risk." The compassionate part of my head says "why the fuck do we talk about other human beings with such a callous disregard for their sum."
That Guy was repeatedly reduced to a set of skills and institutional knowledge. Leadership feared he would die and that would negatively impact the business. Leadership didn't give a solitary fuck about his life.
He was one for the first 50 employees in the organization. He was the second or third longest serving member of the company. He was a pragmatic, overworked sysadmin who was mistreated and undervalued, and put in a position to engineer the majority of the infrastructure of a multibillion dollar company single handedly.
tech, activism, looks like a subtoot but isn't meant as one
Please, tech people, learn the lesson that startups and other tech companies will only hire you and fund your 'social good' work for as long as it makes business sense for them, regardless of what they promise, and that you really do actually need to build your own community infrastructure that doesn't rely on corporate funding!
Sure, if someone offers a bag of money that can be put to good use, and accepting it doesn't come with strings, go for it - but you really need to be working on your own thing in parallel instead of expecting your employer to keep bankrolling things forever. Corporations are not your allies in social matters, no matter how friendly a face they put on.
(This was inspired by a toot elsewhere but is not intended as a subtoot of that - I've been seeing this pattern for years now and most people don't seem to be learning from it)
"Removing focus indicators for keyboard users is like hiding the cursor for mouse users." - @matuzo in Web Accessibility Cookbook
Brilliant comparison!
In fact, it made me wonder... can you hide a cursor for mouse users? Yep, you can set it to a custom png file that's completely transparent.
If you want to see for yourself how annoying that is, visit https://nonvisualwebsite.com/ #a11y
about FOSS and paying for software
Every once in a while there are calls to "pay/charge for your FOSS software because developers" need to eat, and while that's true, it's not really that simple either.
Poverty can be seen from (at least) two perspectives; income and expense. On the one hand poverty can mean having no or insufficient income, or being a victim of eg. labour theft. But it can also mean being unable to afford the things you need, or them being so expensive that you don't have enough money left for other things.
These are really one and the same thing when it comes down to it, but the point I am trying to make here is that there's more to it than just not getting paid. For example, consider people who use FOSS software *because* they cannot afford to pay for software.
None of this changes that developers need to eat, and that people should be paid for their work, but it *does* mean that you should think carefully about *how* to do it - maybe charging a flat purchasing fee is not the right option. Pay what you want? Income-dependent cost? Donations? Regional pricing? Free licenses under certain conditions?
There are lots of possible ways to approach this in a way that the developers are fairly compensated *and* you are not excluding people from your community or software based on their wealth; but the important thing is that you actually think about the right option here, and don't just leave it at "charge for the software and consider the problem solved".
Likewise, how are you dealing with dependencies? It's easy to charge for end-user software, but charging for libraries is much more difficult - even though those often do a lot of the heavy lifting, and a lot of expertise and work has gone into their development. How will you ensure that *their* developers get to eat too?
You don't need to always get everything right the first time, but be cautious of simplistic narratives that only say "pay people for their work" and leave you to draw the rest of the owl. There's a lot more to it than that.
Can anyone recommend me an *offline* horizontal timeline-making tool?
I'm looking for something akin to TimelineJS or Tiki Toki (pictured), to visualise some periods of my life, but given the current state of internet scraping, I don't particularly want to upload a bunch of personal info to someone else's server.
I'm not after Gantt charts or vertical-scrolling timelines.
(Open source would be ideal, but I'm willing to buy a product if it's good enough.)
“The Woman Who Could Smell Parkinson’s - The New York Times”
This is amazing
#OnThisDay, 13 Aug 2014, Iranian mathematician Maryam Mirzakhani won the Fields Medal for her work on complex geometry. She was the first woman to win it since it began in 1936.
She died in 2017, aged just 40. Multiple awards and initiatives are named after her.
@tshirtman @quietmarc @SallyStrange There was a meta data paper where someone studied all the papers on archeological digs as a whole and worked out that something was wrong because something like 80% of all bodies were “male” which obviously isn’t right. So they went back and reexamined findings and basically because gender from physical remains was somewhat guesswork they based gender also on grave goods which, of course, was a circular argument. Now they are better at it (not perfect) so we now have female roman gladiators found in London, Shield Maidens found in the north of England, and a Galli follower of Cybele (trans woman) also in Northern England.
Finally resumed work on my "booleans as a service" platform for enterprise.
In the free edition of the API, a `GET` to `~/Values/True` will return `1`. Rate limits apply.
In the professional tier, you get the features of the free edition, but also, a `GET` to `~/Values/False` will return `0`, plus, rate limits are higher.
In the enterprise edition there are endpoints such as `~/And/1/1` (which returns `1`!), and many more endpoints. All of these, of course, depend on an LLM.
Technical debt collector and general hype-hater. Early 30s, non-binary, ND, poly, relationship anarchist, generally queer.
Sometimes horny on main (behind CW), very much into kink (bondage, freeuse, CNC, and other stuff), and believe it or not, very much a submissive bottom :p
Feel free to flirt, but if you want to actually meet up and/or do something with me, lewd or otherwise, please tell me explicitly or I won't realize :) I'm generally very open to that sort of thing!
Further boundaries: boosts are OK (including for lewd posts), DMs are open. But the devil doesn't need an advocate; I'm not interested in combative arguing in my mentions. I am however happy to explain things in-depth when asked non-combatively.
My spoons are limited, so I may not always have the energy to respond to messages.
Strong views about abolishing oppression, hierarchy, agency, and self-governance - but I also trust people by default and give them room to grow, unless they give me reason not to. That all also applies to technology and how it's built.