HNHacker News
TopNewBestAskShowJobs

pclowes

1,037 karma · joined November 30, 2024

submissionscomments
pclowes··on Trot
I feel its hard to articulate how broken react/typescript/the front-end ecosystem generally is unless you do a project with another paradigm.

I did an iOS app for a fairly important production use case around 2017 and once I relaxed and did the work to slow down and learn instead of just trying to get functionality to work it was a great experience.

I lost almost all taste for FE when react came around (elm was fun). Felt broken then, feels especially broken and taped together now. Somehow still the default.

pclowes··on Amazon's killing a feature that let you download and backup Kindle books
I am weary of corporations still trying to own everything they already sold me. Additionally sick of them trying to control speech and thought based on whatever ludicrous corporate nanny culture is in vogue.

The people censoring books with “inappropriate language” have no understanding of precedent, history, or art. 1/100th as talented as the authors whose work they “update”. Their life’s greatest accomplishment is making something actually impressive slightly worse.

Coincidentally I was already looking at a Kobo Libra Color or a Supernote Nomad, this just sealed that decision.

pclowes··on We replaced our React front end with Go and WebAssembly
Honestly, I think it is because the Scala community was/is/can be so pedantic and bickering and often combative and toxic that it lost all momentum and appeal.

Nobody wants that culture in their workplace. Also the dysfunction is visible in the technical fragmentation of the ecosystem

pclowes··on The FizzBuzz that did not get me the job
Most leetcode questions are just asking if you can recognize the same 15 core CS algorithms in different situations and pick the right one.

A few have a trick or insight but I haven’t ran across those in interviews.

pclowes··on The FizzBuzz that did not get me the job
I think if that was an honest description of the interview question then that alone indicates insecure B players _at best_.
pclowes··on Engineers do not get to make startup mistakes when they build ledgers
I think “make it work, make it right, make it fast” is a solid approach.

It appears the startup in question just never even did step one. A financial system that is imprecise does not work.

Additionally that mantra is typically applied at the story/issue level in my experience as in:

1. Get the tests passing 2. Get the code clean 3. Identify scaling bottlenecks and remedy if necessary.

← PreviousPage 8 of 8