HN user

lrobinovitch

213 karma

theleo.zone

Posts7
Comments64
View on HN

https://shareourpics.com/

A focused and functional service for event hosts to collect guest photos through a shared link/QR code that leads to an upload page. Think photo gathering for weddings, bachelor/bachelorette parties, corporate events, big birthdays, etc.

There are many of these out there, but I found most unintuitive ("too complicated for Grandma"), too featureful, and/or much too expensive.

Author here!

If I were to give this post a longer title, it would be "I made a terminal pager because I needed a really good viewport component for my Go TUIs, then realized that a TUI viewport is just a mini terminal pager and I want the same text navigation and manipulation experience everywhere that I encounter long text blocks in my terminal".

I take no issue at all with `less`, it's super powerful and configurable as I call out in the post. I took the functionality I needed, made it a reusable component for Go TUIs, then made a terminal pager in the form of a Go TUI with it.

What exactly drove you nuts? The python ecosystem is very broad and useful, so it might be suitable for the application (if not, reasonable that you'd be frustrated). With strict mypy/pyright settings and an internal type-everything culture, Python feels statically typed IME.

Jujutsu for everyone 11 months ago

That makes sense, good to know, thanks.

I basically always force push

How do your colleagues deal with this, or is this mostly on experimental branches or individual projects?

Jujutsu for everyone 11 months ago

You have to force push each time you do this, right? How do your coworkers find the incremental change you made to commit 1 after you force push it, and how do you deal with collaborative branches effectively this way? And if I don't want to work this way and force push, are there other benefits of jj?

It's unclear to me what you're defining as real. Coal mining? Childcare? Community centers? Through hiking? Interesting theoretical realms can have enormous consequences in the physical/tangible world, as I'm sure you know :). Maybe it's more of a "presence factor" in relation to this story: a measure of how aware you are of the roles and responsibilities you have and how engaged with them you are.

NYC was also my least favorite part of Recurse. I had to move 2 weeks in because my first apartment was right next to the train.

I absolutely loved Recurse though and credit it for a lot of my development as a programmer and it's my favorite programming community.

Luckily you can also do Recurse remotely now!

This github issue is often linked when this topic is discussed: https://github.com/github/gh-ost/issues/331

Personally, it took me quite a few years to make up my mind about whether foreign keys are good or evil, and for the past 3 years I'm in the unchanging strong opinion that foreign keys should not be used. Main reasons are:

* FKs are in your way to shard your database. Your app is accustomed to rely on FK to maintain integrity, instead of doing it on its own. It may even rely on FK to cascade deletes (shudder). When eventually you want to shard or extract data out, you need to change & test the app to an unknown extent.

* FKs are a performance impact. The fact they require indexes is likely fine, since those indexes are needed anyhow. But the lookup made for each insert/delete is an overhead.

* FKs don't work well with online schema migrations.

Ten years isn't seeming nearly long enough anymore.

I'm getting better at feeling energized by this view rather than sad and overwhelmed. Something about embracing my inner dummy and keeping the beginner's mind attitude at the forefront.

Every day I interact with coworkers who know way more about computer stuffs than me and coworkers who I know way more about computer stuffs than them. We are all on this exciting bottomless journey of knowledge and mastery together and it's awesome.

Each level of abstraction unveiled is itself interesting, even if it's still hundreds of layers above the ground floor. Reminds me of the Feynman quote “Everything is interesting if you go into it deeply enough”.

I feel lucky to have found a career in which I enjoy the minutia as well as the bigger picture, and it also happens to be able to create incredible real world value when applied to the right problems in the right ways.

converting to veganism would greatly outweigh 10% of a median salary to the most effective climate charity

This claim itself is based on probabilities assigned to the potential impacts of veganism and donations. I would argue that this is a form of practical utilitarianism - assigning probabilities of event occurrence, weighted by their negative impacts, and attempting to do the most good despite the uncertainties and evolving information landscapes.

assumes capitalism as an immutable reality

I would reframe this as "in practice, as an actually existing movement, recognizes that capitalism is our current system, and in order to create less exploitative, inequitable, and unsustainable systems, one has to engage with it to a large degree".

How can new, better systems be set up today without funding something in the global capitalist system? The article suggests that anyone with better ways of doing good per-unit-time or per-dollar should be evangelizing those rather than dismissing the efforts of others who have some current answers to those questions, and are probably open to better answers as they come up.

When people (me included) criticize EA for it's questionable priorities, it's an expression of exasperation, not an existential attack on the movement or its practitioners.

I have had different experiences with critics of EA. Many critics come off as passive, finding one or two basic disagreements with institutions or moonshot/futurist ideas that they use to justify their total disengagement with their potential positive impact in the world beyond themselves and their friends/families. You might not even call these folks critics - maybe they're just "excuse-seekers"?

It sounds like you are a critic who is actively engaged at the second and third blocks of the tower, which I assume the author would have no issue with.