With a type checker on, types are fantastic for catching missed cases early.

Oh yikes. I did not know.

Comments URL: https://news.ycombinator.com/item?id=44962420

Points: 2

# Comments: 0

For me it's not uncommon for AI to draft an initial solution in X minutes, which I then spend 3*X minutes refactoring. Here's a specific example for a recent feature I coded: https://www.youtube.com/watch?v=E25R2JgQb5c

Comments URL: https://news.ycombinator.com/item?id=44864467

Points: 96

# Comments: 39

Edit: Perhaps this is a reminder that custom fonts are a potential attack vector for security-sensitive websites since font rendering runs highly-complex programs, probably in a language that isn't memory safe.

Comments URL: https://news.ycombinator.com/item?id=39807228

Points: 1

# Comments: 2

  1. Maybe -> Optional[T]
  2. Result -> Union[SuccessT, FailureT]
  3. Future, FutureResult -> concurrent.futures.Future[T]
  4. IO ->  don't use this; none of the standard library I/O supports it

I also appreciate the typechecker enhancements being put forward by their custom plugins.

> It's tempting to imagine some rules like: no ads, no popups of any kind, government mandated or not, especially no cookie banners, no paywall, but even sites like Wikipedia fail at those criteria today.

This sounds like the approach that the Marginalia (https://search.marginalia.nu/) search engine is taking. My understanding is that its algorithm favors text-heavy sites. And additions to its index are done via GitHub Pull Request so it's effectively using an approve-list (whitelist).

BBEdit I still use for multi-file search & replace since I prefer its interface for that. It also has the fastest typing speed.

PyCharm I use exclusively for identifying & removing unused imports in Python.

VS Code I don’t use at all. Relatively slow typing speed. Relatively slow navigation.

This way I can focus on what I want to watch and not worry about how I will watch it.

Much of this complexity I eliminate by using the Immutable Server pattern:

Specifically I deploy my app as a Docker container hosted on a virtual machine cluster managed by AWS ElasticBeanstalk. OS upgrades and patches (outside the container) are done by AWS.

If anything goes wrong with a VM I just terminate it and a different fresh VM spins up to take its place.

I prefer the “explicit is better than implicit” norm in the Python community over the “powerful yet mystifying magic” I find in Rails. (This is personal preference.)

I also appreciate Python source code being easier to manipulate with tools than Ruby, since Ruby did not have a formal grammar the last time I checked. Any tools that did exist appeared to usually include the yacc/bison file from MRI (the main Ruby implementation) as the best approximation of a language definition.

* BetterSnapTool for window snapping and maximization (although I prefer Moom for better control).

* Afloat to force a particular window to always be on top.

* TinkerTool to mess with various other settings.

Sure, these may not be “built-in” as first party capabilities, but Apple has a history of slowly bringing such capabilities into the OS over time. Flux (for altering screen tint at night time) became standard. So did TextExpander (for auto-expanding abbreviations).