ohmahjong

That's a great point, it really is all about tradeoffs. In my use case there is strong motivation to keep data creation times low, so writing out multiple datasets comes at a product/opportunity cost moreso than a storage cost. Thanks for the insight.

This is a bit off-topic but I'm interested in the same space you are in.

There seems to be an inherent pull between large chunks (great for visualising large extents and larger queries) vs smaller chunks for point-based or timeseries queries. It's possible but not very cost-effective to maintain separately-chunked versions of these large geospatial datasets. I have heard of "kerchunk" being used to try and get the best of both, but then I _think_ you lose out on the option of compressing the data and it introduces quite a lot of complexity.

What are your thoughts on how to strike that balance between use cases?

Some books are especially suited for multiple passes. Every time I reread a Discworld novel, I find new jokes or references that I had missed earlier.

Touching on your lack of comment on the paint job, I have seen one instrument (a guitar) painted with a delightfully kitsch Elvis portrait. It was a gift to a musician by his lover, but it affected the tone of his guitar so much. They had to tearfully scrape the whole job off before he could tour with the instrument again.

I saw this described recently as the "Lambda Pinball" architecture.

* https://www.thoughtworks.com/radar/techniques?blipid=2019110...

I use ChatGPT sometimes outside of work too, for hobby projects. I'm finding it much less useful for frontend work, partially because it's not a domain that I'm as familiar with and so the shortfalls in the code don't immediately stick out to me. It's good for writing specific things like "write a typescript function to connect to Google Sheets and write x data to a table"

I try to use it as often as possible as a rubber duck. It feels sort of like pair programming with someone who has a pretty good idea of how most common libraries work, but where the details are fuzzy and a bit outdated.

The HR team uses it all the time to generate initial drafts for job descriptions and the like.

A member of the product team pointed our API documentation at it and asked it to write a simple query. 99% of the code was correct, except it used the wrong header for authentication. Lo and behold, that was something we hadn't documented very well!

We did an employee survey a few months ago on who was using AI tools and how, and I'm confident that usage has gone up significantly since then. I know mine has.

I have personally found the rubber-ducking to be really helpful, especially for more exploratory work. I find myself typing "So if I understand correctly, the code does this this and this because of this" and usually get some helpful feedback.

It feels a bit like pair programming with someone who knows 90% of the documentation for an older version of a relevant library - definitely more helpful than me by myself, and with somewhat less communication overhead that actually pairing with a human.

It's much more noticeable when running locally. Going from something like black + pylint + mypy running in a pre-commit hook to black + ruff + mypy has been wonderful for me.

It lets me actually set up another terminal session to run ruff on every file change - where pylint would take seconds, ruff is essentially instant.

Side note: I really hope mypy can get the same treatment; it runs quickly once its cache is established, but it's terribly slow running from scratch.

I think scanning receipts (which still requires manual effort) or parsing bank SMSes locally could work

Does that work now? I seem to remember having to use `tags: list[str] = Field(default_factory=list)` a lot

That was very informative - it certainly does not give me the motivation to build my own billing system, but it does shed light on the scope of the task.

Side note: Is "I don't want to write/use a billing system" a compelling reason to release software for free?

When it comes to generating diagrams that look nice from just about any diagram scripting language, I tend to go to "Kroki!". Hopefully they'll do some work to support D2 as well, although going from D2 -> PlantUML is something you can do in the meantime.

* https://kroki.io/

There must be some diffusion/refraction from all of the atmospheric particles as well, right? I don't think you'd be able to see it as a bright rectangular object so much as a bright fuzzy blob in the sky.

Here is another excellent breakdown by Joshua Comeau, who is my go-to for all things CSS-related. He goes over the practical cases where you do want to mix and match units, how browser zooming affects accessibility, etc.

https://www.joshwcomeau.com/css/surprising-truth-about-pixel...

Here is the benchmark section of the site, although I don't see a definitive source for what is being run.

* https://turbo.build/pack/docs/benchmarks

I 100% agree - I don't think that I would ever reach for a PoW blockchain to solve this problem, but it has certainly generated some interesting discussion

Is the demo site still supposed to be up? I see

> TypeError: path must be absolute or specify root to res.sendFile

when I try to visit it.

cottenio is the author in this case.

If there is the potential of internal employees being malicious, then maybe trust isn't guaranteed.

Time for some deep thumb-twiddling

I think that you've hit the nail on the head with trust. I have felt most productive in small teams with a lot of autonomy and self-regulation. The most interesting problem to me is how to establish that trust in the first place; especially if team members have varying levels of "conscientiousness" regarding code and process

The sound of "gigadollar" really tickles my fancy. Is a penny one centidollar or ten millidollars?

I didn't think it would work for me, but I have turned into a daily user of http://lofi.limo/ . The number of tracks isn't too high, but I love the somewhat goofy interludes and the ephemeral chat interactions.

I've been explicitly told on a phone interview that "we really wouldn't be considering someone of your experience without the referral". Nailing the technical interview and getting the job felt amazing, but that referral came in _clutch_.

Yes, in this case that is correct. It is common to play the same note on two different guitar strings in order to tune them together.

This has been my experience as well, as someone who added a pre-commit hook (black and mypy) to a repo in lieu of adding it to CI (it was a while ago). I came back to the team a year later to find that everyone had simply disabled the hook, and forgone typing/formatting entirely. A day or two of fixing formatting, type hints and linting errors later, the CI pipeline had a new step enforcing all three :)

Thank you for sharing such an incredible story - I would never have expected to read something so entertaining in the comments of a post about mouse splenectomies.

"The beginning of the dividEnd", maybe?

Thank you everyone for the _really_ helpful responses!

It is immediately apparent to me that my interaction with vim has been heavily informed and limited by my preconceptions and previous text editing experiences.

Time to start engaging with vim as its own entity, with its own conventions and idiosyncrasies.

EDIT: Formatting

I relate quite heavily to this when using vi to do all my git-related activities.

git rebase -i ...

followed by

↓dw ↓←dw ↓←dw ↓←dw ↓←dw ↓←dw i s ↓s ↓s ↓s ↓s ↓s

because I keep forgetting :s/pick/s/g is a thing

i, a, :q, :wq, dd, xdd, and D are all the ones I remember, but cutting/yanking pasting is still something I don't have the muscle memory for.

Shift+G takes me to the bottom of a file, but I don't know how to get back to the top :D .

I really need to make time for vimtutor and commit to it.