Even though the keys _are_ there I have no muscle memory for the modifiers on my right hand.
1,172 karma · joined February 14, 2013
Even though the keys _are_ there I have no muscle memory for the modifiers on my right hand.
metaphors are impossible. never use them. they are meaningless.
unlike creative industries, there's a fuckton of toil work that just needs to be done automating processes. the playbook style excels there, and unlike artistic work there's not really room for memorable standouts that break the rules.
music will always have the quality where good novelty is impressive and breaks boundaries. business processes less so. prince can (could) deliver a stellar rendition of purple rain that breaks the bonds between heaven and earth even though you've heard the song before, but ain't nobody delivering a stellar automated check deposit workflow execution that stands out from the rest.
commodity services bring commodity work. this is fine. i do not want my mobile check deposit to be a tour de force, i want it to be something i don't give a second thought. there is beauty in the blase' being blase'
IMO it makes more sense to communicate the expected impact of the changes, so that downstream can read a patch bump as unlikely to cause issues.
crypto can hypothetically be every bit a brilliant new wheel paradigm as the marketers would suggest (it isn't, but whatever) and that won't stop entities with legal authority to eviscerate all current corporate entities associated with it from doing so (they are).
ya'll wanna believe that binance and coinbase can fight the massive legal assault on their business practices and come out on top simply by virtue of the nobility of the crypto ideal, go right ahead
Those fuckers are well aware of their captive markets and extract rent like no other. The licensing costs on such an outdated piece of technology are obscene.
given a day or two, sure, I can go review, find that solution, and provide an implementation and explanation as to why it matters for a particular problem domain, but an hour-long phone interview isn't gonna check that effectively, unless they really want to see the initial stage of me silently reviewing maths literature to awaken knowledge in cold storage
on contrast, I _can_ explore systems design stuff fine in that space of time, because systems design _is_ what I practice regularly in industry, because that's what I'm regularly asked to do.
The anti-circumvention provsions are also a trash fire. DRM regimes are some hot consumer-hostile bullshit that have no (legal) alternative because the law is behind them and heavily weighted towards the needs and wants of major IP holders. Modern US copyright law is designed primarily to maximize profits and enforcement mechanisms for entrenched interests with little regard for anything that isn't, idk, Beyonce tier of actually needing that much licensing cruft.
There's some joke somewhere about ours being the first few generations to systematically deny ourselves access to our own culture because biglaw is more than happy to cut off its cultural nose to spite its face so long as the money train keeps flowing for the few elites that really benefit from the current system. We have a walled garden that will likely never fall because life is peachy if you're inside the garden already, and anyone outside can't compete with the financial and lobbying muscle of those inside it without operating in legal gray areas at best.
my protests against requiring this, as additional friction for our OSS contributors especially, unfortunately fell on deaf ears. unfortunately i just don't have the energy to beat my more pedantic coworkers over the head with the notion that if these additional formatting rules are that important to them they need to do the legwork to pull them into mainline gofmt
nah, that's actual work. an additional hurdle in the dev environment for some random formatting things that nobody will ever notice though, you can enforce that in a few lines of CI scaffolding, so into the checks it goes
Got to the venue to discover that I now had two will-call tickets, since that's how I'd originally purchased the first one, but TicketMaster somehow broke that record on their end.
Never encountered that level of bullshit from any of the smaller providers. TicketWeb was great when I lived in a market where they were the majority and Eventbrite is fine AFAIK. But now I live in a major market and TicketMaster is the only option for all but the smallest venues. What are you gonna do if you don't like them, anyway? Buy out the venue yourself?
i can't claim to _understand_ it half the time, but there are big rows of mechanical automatons galore
- allow clicking hyperlinks
- allow copying content to paste elsewhere
- adhere to device display preferences. you wanted dark mode? fuck you, my screenshot's black on white, dwi
- support screen readers. i loled hardcore at the other post suggesting twitter OCR them--i mean sure, as a practical matter, they should given the status quo, but YOU COULD HAVE JUST USED TEXT TO BEGIN WITH
- scale properly when zoomed in or out
- display all the text up front. virtually all of these require you click through each image because the thumbnail is cropped (if not too small to read anyway)
idk what reason you'd ever actually want to use them unless you desperately needed to show off the cool font you used. saying they're easily readable is like saying the abhorrent mandatory training videos featuring some extremely bored person reading a script over a static background for 30 minutes, with no option to speed up playback or fast-forward, are perfectly understandable. like, yeah, sure, they _are_, but also you could have provided a set of text bullet points about how not to violate USFCPA that any literate person could read in about 2 minutes and we'd all learn the same damn thing
this does seem about par for the course for Epic installs, which suffer a great deal of typical enterprise software disease. i have fond recollections of their user-facing staff training including a dedicated section for "how do i, a new grad with a sociology degree and 3mo of EMR training, convince a bunch of decade-veteran nurses and physicians that i have enough industry knowhow to effectively advise them how to navigate their complicated EMR install?"
if not a in-person protest, this did remind me of an extremely early 2010s meme format on the subject: https://www.youtube.com/watch?v=dt1BPvMbNpk
Well, who should? Is anything with the authority going to or even inclined to in the slightest?
Cloudflare has maintained a lobbying/policy department since quite early on, but I'd argue that the post from the 31st wasn't so much that there _should_ be policy against this than that there simply isn't. Given the coming EU DSA or, hell, the comical farce that is/was Texas HB20, it seems clear that further government regulation of online speech is coming in some capacity. How is Cloudflare discussing these issues with lawmakers? Are they taking the approach that existing law and enforcement mechanisms are fully sufficient, or are they arguing that there is a common strain between KiwiFarms, 8chan, and the Daily Stormer that has demonstrated a known pathway between speech and violence that needs some sort of updated legal framework?
in a post that further goes out of its way to say, "look at these morally good things we're doing (Galileo and Athenian) that aren't themselves part of the abuse process, and then has their logos as two of the three images in the article body? Okay, sure, this may not strictly be marketing material insofar as it's not an ad the marketing team purchased, but c'mon, did ya'll put those in place to help explain the abuse process or because they're nice "but look, we also do good things!" window dressing on an article you think otherwise may not have the best reception?
i despise this given that there's nothing like the bump mechanic in channels (threads with newer posts don't move to the top of a list, they just stay in their original chronological order), and in the thread view where there is, you can't keep threads uncompressed, there's no pagination for threads with 100s of messages, and finding individual threads is a chore because they're still not completely compressed.
No, they exposed just what _someone working at Netflix who produces AMIs for Netflix's infrastructure and is required to conform to assorted Netflix expectations lest they be told to go pound sand_ needs. Accepting that constraint makes the problem much easier. When you try to make a general-purpose tool, you rapidly run up against:
- Some other user needs to do something that you don't, that the existing configuration surface cannot possibly account for. You now have either a tool that exposes two (and soon, three or four or five ad infinitum) means of doing thing (likely without any indication why you'd use one or the other) or a tool that exposes <original means of doing thing> and <fill in your own thing from scratch>.
- Someone has other parts of their infrastructure whose design is, for lack of a better description, "fucking stupid". They don't have the power or will to change that, but they're happy to ask you to include a workaround for it in your product. They also have a number of friends whose surrounding infrastructure is similarly fucking stupid, and some of those are important contracts where sales will force your hand to build the workaround instead of asking the customer not do fucking stupid things.
Yes, a single well-managed organization can delegate various pieces of complexity throughout the org and avoid having other parts worry about them. General-purpose tools do not have that complexity. The reason you have to learn new concepts and tools to learn Terraform effectively is because you're taking all the complexity of dealing with a cloud services provider and then adding an additional layer of complexity on top to augment the things you can do with the cloud provider. The value proposition is that this still better than what you'd do by hand and, crucially, something that other people who know Terraform can understand. Realistically, you can hire another engineer who's familiar with Terraform. You can't clone Matt.
For every 1 person who got a big payout, there are 99 more that just worked themselves to burnout and maybe got a mediocre options payout worth about 1/2 the salary they'd have made at BigCo.
This is probably more true if you're employee number <10 and stick with it through the long haul, which may not be appealing for a variety of reasons. It can also be true if you spin a personal project into a business, but you can do that while employed anywhere.
There isn't any guaranteed, or IMO even likely expectation of a big reward if you join SmallCo and simply "work hard". The reward for that is usually more that higher-ups recognize you're capable and choose you as the go-to person any time they have any sort of tough problem. This is both exhausting and frustrating if you're the designated hero fixer but cannot convince leadership of broader changes they need to make to limit the number of fires that need fighting or train other employees to handle tasks as effectively as you. The general rule that you'll most likely see a salary increase by hopping jobs anyway still applies.
I don't like the playlist (and now, TikTok)-driven market--I too prefer listening to a full album straight through--but there's not really anything more inherently musical about the formats that came before. For better or worse, that's just the nature of the industry.
OIDC builds on OAuth2 to fill in those gaps with prescribed details and add additional systems necessary for a workable federated auth system. it _should_ be possible to use it entirely provider-agnostic fashion, but in practice it's like any complex protocol with optional parts in that implementations have incorrect bits or idiosyncrasies (why does Azure's provider sometimes serve public keys it doesn't actually use to sign tokens in some modes? god only knows) and you'll probably only provide integrations for a subset of providers, not just let anyone with a discovery link show up and use it.