wooly_bully

Two requests!

1. unique urls per channel so I can send it to a friend and say "check this out" 2. up + down keys for changing channels

The sensible route to this today is to use a query client, IMO: tanstack, rtk query, apollo, etc.

It prevents the umpteenth reinvention of an incomplete fetch state machine, which is probably the number one most consistent frontend bug I encounter.

The wording virtually guarantees that it’s changing to subscription. I give it a year and a half.

Guess I'm one of the annoying users who complained when armin's Lektor (https://github.com/lektor/lektor) started going dormant back when, but I loved it for a while. I'm on Astro now, but a big thanks for helping a younger version for me.

The book that Dominik Tornow is writing “Thinking in Distributed Systems” has been an excellent next read after DDIA for me (it’s not yet finished I believe).

Really shows the experience of someone who understands this stuff inside and out (was one of the main people behind Temporal).

I don’t think this would help if your goal is not rapidly increase housing costs. If covid proved anything about the housing market, it’s that theres a housing shortage everywhere. Plenty of LCoL areas still have disproportionately high housing costs compared to median income now. When remote work was required, people fled cities and led to housing crises in areas that aren’t just major cities.

Great piece from M. Nolan Grey, who is an excellent twitter follow: https://www.theatlantic.com/ideas/archive/2022/08/housing-cr...

Talent board link: https://coda.io/d/Talent-Board-2-16_dpUo3fTL8Ev/Candidates_s...

(Ex-)Convoy engineer here. No mystery as to why this happened, sudden tight market and low available capital demolished us. External reasons given in the article were the same we knew and couldn't do anything about considering that none of the M&A options materialized.

Detailed the shutdown on a call at 8:30am Pacific this morning. CEO said there'll be no severance or healthcare.

Lot of talented folks in Seattle and beyond who'll be looking for new gigs.

This is what Svelte does, React has a runtime even when bundled

It’s good for reference but not for discovery. If I already know the general concept (let’s say Template Literal Types) I can get good info on it, but if I start with a question like ‘Is there a way to make sure this string literal starts with “id_”?’ then I find it very hard to know.

Random but this is what I’m finding GPT-4 best at: translating random questions into domain terminology + providing examples.

I just am about halfway thru. Absolutely stands up, doesnt even feel dated almost 20 years after the revised edition.

On a similar note - If you’ve not seen it, the galata bridge in Istanbul has a boardwalk full of shops on its underside. Very cool.

Not sure if I agree with some of the specifics of this, but the overall sentiment is still valuable. There's a lot of work out there for non-youngsters looking to get into software development. Lots of hiring companies will value your experience even if it's not directly related to coding.

Wrote these just after I switch careers ~4 years ago:

1. https://zmsy.co/blog/career-switch/ 2. https://zmsy.co/blog/switching-careers-to-software-engineeri...

Not a book, but the History of Science series from Crash Course on youtube is very entertaining.

H3 tags on this could really use a bump in size and contrast from the regular text.

Your last point on the correct code running, ugh. I haven't gotten better at it even thought I'm aware of it more now. Had an incredibly persistent linting config issue just last week, turns out I had the wrong config open for editing in vim.

WSL is not 'native' per se, but it's very well-integrated with Windows. I'd give it a look, even if it's just writing a script to run a build command in WSL from the same directory you're developing locally in.

That's good to know at least; will give the go API a look. The latter option you're recommending is essentially what I went with (Node bin script that shells out to run cdktf commands).

The 'not using HCL' bit is really the only positive I've found so far because everything else has been more difficult than just using TF directly. I think my goals were slightly off from the beginning, because this is really just replacing one CLI with another for me at this point.

What I want: Use Terraform programmatically, i.e. call "cdktf deploy" or similar FROM node or python and give users some scripts they can use where I can abstract away some of the difficulties of learning to use Terraform natively for simple use cases (i.e. deploy an S3-based frontend host). Ideally, I had intended to distribute some npm-installable packages which would run this stuff.

There's TONS of use cases for Lambdas where the operational costs (both in terms of time/energy/expertise and to lesser extent monetary) of running something persistent are much higher.

In my last gig, we ran plenty of services that would never need to scale and would likely never hit the point where Lambda became too expensive. Low-utilization services (Example for order submit, because we only ever got a couple hundred orders per day), Cron-type jobs (Admins could use Cloudwatch to monitor), Temporary fan-outs using queues. Anything that won't ever hit the millions-per-day level is a good candidate for something along these lines. Most of those services cost <$5/month.

In my experience, it's not the time required but that a lot of development teams don't have a sysadmin or ops skillset.

In the linked figure in the article, the SK tests have about 5x more per million people so their denominator is likely a better idea of the true number of cases.

Lots of reasons to love a visual debugger:

- Easily set breakpoints and localize faults quickly.

- Enter the debug shell and evaluate statements based on the current program context.

- Tinker with variables at runtime and see how the code responds.

- Conditionally catch things that are going wrong and evaluate program state at the time.

- Simulate difficult-to-reproduce things like race conditions by messing with program state.

- Use it like a CLI to do stuff from the program, like send requests using the actual program code.

Seconding this. Big fan of Dokku on a DO droplet as an inexpensive way to make applications.

The "spin up a big data cluster" bit at the beginning seems like either a straw man or just oddly out of touch. Who, when determining how to process something on the order of a 100gb file, even considered something like that?

Also, SQLite is a first class citizen in this space. Most if not all languages can easily load data to it, virtually any language used for analysis can easily read from it, and it's file-based so there's no reason to spin up a server. Finding 100GB on disk is much easier than 100GB in ram.

Yeah, my normal Gitlab workflow is:

1. Start a branch with a first commit 2. Open a PR and write details / background 3. Mark WIP 4. Eventually remove WIP and add someone as reviewer.

Glad to see this is available now.

Good point.

If GG&S changed the way you think, I'd highly recommend following it up with either the book from that review (Eric Wolf's "Europe and the People without History") or Ian Morris's "Why The West Rules, For Now".

Strongly disagree. The geographic determinism theory of GG&S is frustrating and ignores significant factors in the rise of the West.

This review is something I generally send out to people after they've read GG&S, and strongly recommend Eric Wolf as an author. He puts many of the points I would make significantly more eloquently:

https://www.livinganthropologically.com/eric-wolf-europe-peo...

I'm frustrated being on a 2016-era MB Air and feeling like I don't anything to upgrade to without a touchbar now.

Once this machine kicks the bucket, I may just buy another of the same one instead of upgrading (if they still sell it by then).

You've got some citizens of Null Island in your data!

https://en.wikipedia.org/wiki/Null_Island