whstl

29 ms·

751.
by whstl 1y ago
> "got no money? Use other people's money! Pay $300 to learn how" Commendable that a grifter is actually following their own advice!
752.
by whstl 1y ago
In the microservices world this is the monolith itself sitting in the center :/ Even in architectures that start as distributed, I’ve seen the “involuntary monolith” arising. Way too common, unfortunately.
753.
by whstl 1y ago
Casey’s presentation was great, and demonstrates the problem I was talking about: a lot of those complex things lose something when they become “pop culture”. A lot of people never read Fielding’s dissertation or is aware of the monad laws
754.
by whstl 1y ago
I said “Later interpretations of Monads”, I did not say “monads”. Fielding’s dissertation is fine in itself. The web itself, AtomPub, OData, among others, all follow REST and HATEOAS. Same for Monads: the laws are fine and the implementat
755.
by whstl 1y ago
> The problem is when implementations aren’t actually monads at all Exactly, this was my point, it wasn't clear. The original definition, and Haskell's implementation are good in itself. Monads in Haskell are not that difficu
756.
by whstl 1y ago
> As far as I can tell, he's not even describing an "API" as we'd normally use the term today. For all practical purposes, it's pretty much just "using an HTTP server and hyperlinks to let (human) users dis
757.
by whstl 1y ago
Clipping the quote like that completely changes the meaning of what I said. I didn't say that. But I stand by what I actually said: Smalltalk's OOP is indeed very novel, even for today, especially compared to C++/Java, but it
758.
by whstl 1y ago
In the parent comment I did qualify my statement, in it I am talking about monads "once it gets 'explained' and migrated to other languages" , not about Monad in Haskell and definitely not about Monad laws.
759.
by whstl 1y ago
This is perhaps a case where miscommunication saved an entire industry. I once got a new hire from Uber and for months on end his complaint was that “the services are too big”.
760.
by whstl 1y ago
This is another good example. I remember people getting very angry here 10-15 years ago over HATEOAS. In most discussions REST has come to mean “cute URLs” thanks to Rails.
761.
by whstl 1y ago
The original book completely failed to communicate that, though. This is common knowledge today, but wasn’t for a long time.
762.
by whstl 1y ago
Uncalled for. Try to follow the guidelines instead of calling people names.
763.
by whstl 1y ago
This is an oversimplification, and part of the problem I mention. The "big leap" in Smalltalk was the idea that everything is an object and computation is message-passing, not just classes and instances. That’s not from Simula. Si
764.
by whstl 1y ago
It is catching up in other countries, it's a startup thing. Silicon Valley has a reverse-Midas touch, everything it touches becomes shit.
765.
by whstl 1y ago
This problem that MVC has is similar to the problem with OOP itself, with monads, or with some design patterns: the original/popular definitions were so incredibly abstract and disconnected from real life usage that they ended up being
766.
by whstl 1y ago
I mean, yeah. I just said it because this website belongs to YC.
767.
by whstl 1y ago
First: regular employees are already taking the risk of being jobless some time in the future when joining startups. Second: there is no CEO in tech taking a smaller salary than their employees.
768.
by whstl 1y ago
996 is just theater for investors. Saw this happening even at YC companies. There was always that stupid expectation of overworking, staying until 9. The reality is that people twiddle thumbs. And the disorganization and micromanagement pow
769.
by whstl 1y ago
IME, in most cases, it's the dickhead's fault in the first place. This is often a CTO putting pressure on a dev manager when the bottleneck is ops, or product, or putting pressure on product when the bottleneck is dev. The normal
770.
by whstl 1y ago
I saw two projects in a row in a German Fintech (the one that has AI in its name that forbids usage of AI) go exactly the same way. Two/three months to code everything ("It's maximum priority!"), about four to QA, and th
771.
by whstl 1y ago
I also just wanted to build a guitar amp. I worked with EE for a while and it was very boring building stuff. It basically took me changing careers to SWE and working for a games company to finally use the math part of my EE degree. I ended
772.
by whstl 1y ago
Still depends. If the indices are pointing to a dense, flat, contiguous array, it will still be faster than following pointers into scattered heap allocations, with or without prefetching, because of how CPU caching works.
773.
by whstl 1y ago
Some devs have worked exclusively in feature mills where expectations are rock bottom and some senior setups the project for them. When recruiters don't filter them, a basic React test has to.
774.
by whstl 1y ago
The most basic React functionality isn't "React minutiae".
775.
by whstl 1y ago
It was interesting handling frontend interviews recently. We do a 30-min tops exercise where you create a React project to show how to use useState and useEffect, etc. I help with whatever command they want to use and allow Google/Chat
776.
by whstl 1y ago
Agree. These comments sound super absurd to me, because RDS is difficult as hell to setup, unless you do it very frequently or already have it in IoC format, since one needs setting up a VPC, subnets, security groups, internet gateway, etc.
777.
by whstl 1y ago
There are already industry standard codes for songs, albums, performers, etc: ISWC, ISRC, IPI, IPN, ISNI. Spotify already use some of those, but I dunno if they expose via API or make it searchable.
778.
by whstl 1y ago
They would rather give a 10% increase to the guy replacing you.
779.
by whstl 1y ago
I believe you can build great abstractions in this kind of software, but if you want them to survive you gotta keep them any of that away from anything involving the business logic itself. You can only do this on product-like things: auth
780.
by whstl 1y ago
Hard agree. I also worked on some quite large organizations with quite large services that would easily take 10x to 50x the amount of time to ship if they were a smaller org. Most of the time people were mistaking complexity caused by bad d

More ›