301–310 of 391 posts
Earlier quoted context omitted.
> year long journey of 18 hour days I couldn't do it, even if I had the talent. I have to work to get money!
At 18 hours of work a day, your money need are relatively low! Pair that with just sleeping at the office toilet and eating used coffee grounds and everything should be good!
Not to detract from the achievement, that's amazing. Mostly useless, but amazing nonetheless.
Earlier quoted context omitted.
society create the überman myth to keep the working class down, thinking they will never be the top of their game. the ones doing the hiring know that those putting in 18hrs a day are the unicorns, i.e. the best they can hope to find.
I was accidentally one of these once. I fixed a long standing bug that was a companies top priority for several months and no one had been able to fix it. They were talking about re-writing an entire app to resolve it, at a cost of 100's of thousands of dollar, dragging the vendor over the coals etc. I was relatively new and thought I'd take a look, ignoring all the mystique surrounding the problem. It turned out to…
In most cases these issues are a result of similar kind of patching of a previous similar issue resulting in unexpected outcomes. (Probably going on for years)
From my experience management often tries to ignore the bigger refactors by using inexperienced people to patch things repeatedly, meanwhile the team suffocates under technical debt and responsibilities as a result of this mentality.
Sometimes its better to stick with the dev team for long term goals instead of becoming a "management puppet" for short term wins.
Earlier quoted context omitted.
What was the argument for why it couldn't?
Because we lack an infinite tape and infinite time, not everything that is Turing complete can run DOOM
"But I'm not one of those fancy 10x developers. Instead of a master of craftsmanship, I'm more a master of close-enough-manship" I definitely relate to this comment. and he also says "It was a brutal year long journey of 18 hour days" I think people are looking for those unicorn 10x devs that are like Good Will Hunting for code, but forget that there are those devs that might not get things right away but never stop…
Earlier quoted context omitted.
> it's just a set of all possible types `unknown` is the set of all possible types (it's the top type[0]). `any` goes beyond that—it basically turns off the type checker[1][2]. [0]: https://en.wikipedia.org/wiki/Top_type [1]: https://tsplay.dev/mA9vXm [2]: https://www.typescriptlang.org/docs/handbook/2/everyday-type...
Your 1 isn't equivalent to my example, line 11 is not constraining the type.
The `T extends Record` on line 11 is a type parameter constraint though. Are you referring to something else when you say "constraining the type"?
These typescript fanatics never fail to make me feel disgusted by what they've done...
Earlier quoted context omitted.
'any' has always been intended as an escape hatch, so no abuse here [1]. The type representing the set of all possible values (the top type in the type lattice) is 'unknown'. [1] https://www.typescriptlang.org/docs/handbook/2/everyday-type... [2] https://www.typescriptlang.org/docs/handbook/release-notes/t...
unknown is not equivalent to any as a type constraint: doesn't work. https://www.totaltypescript.com/any-considered-harmful#type-...
I've got an issue open about TypeScript's provided `ReturnType` type which is somewhat related to this[1].
> "It was a brutal year long journey of 18 hour days" [to run doom in TypeScript types] This is some serious dedication for what at first blush may sound to many to be a completely unserious, or even useless, achievement. But I say to those people: a DOOM proof is just as worthy of praise as any other academic mathematical proof, and has the advantage of being verifiable by laymen. Congrats on this amazing achievemen…
> year long journey of 18 hour days I couldn't do it, even if I had the talent. I have to work to get money!