nodoodles

If the lift is geometrically full of the (perhaps blended) mass of people, and race-dependent density is roughly similar, does it matter?

Agreed, the negativity here is quite wild.

There are new power tools for our craft. People are experimenting and having fun with said power tools, and have interesting results that may be transferrable to $YOUR_PROJECT.

Doing things just because we can is a great reason for hacking around.

Kudos for the author for answering questions and keeping up resilience - HN crowd is not what it used to be (shakes fist at a different cloud).

Of which calendar system?

Curious but offtopic - are others also immediately suspicious of the content and quality because the readme is so obviously AI-written? What are ways you distinguish genuinely useful contributions on the sea of slop?

Only a 100 years — the whole history before that was working in the vicinity of a home, it does feel natural to return to that. Instead of anvils, we hit keyboards and instead of swords produce alignment, but either way it brings food to the table and allows flexibility in work-life?

Yet another browser-based screen/video recorder and editor but with multiple inputs, full privacy and scriptable effects - a slow weekend project

Here's a bookmarklet:

  javascript:document.querySelectorAll('a').forEach(el => el.style.backgroundColor = 'transparent')

On 2/ there is a safety point in having the grounding pin on all plugs, and it being longer than the live/neutral: in the socket side, the grounding pin opens up latches that block live/neutral, so kids can’t stick things into them..

I generally would agree it is the best plug standard for safety, but clunky and painful to step on..

A little page that tries to keep up with Flickr uploads in real time.. built ca 13 years ago, amazingly still running. http://ekke.si/flickr/?render=random

I have thought of that as ‘n’ being the manageable threshold and the (uncontrolled) ‘+1’ the overflow creates the problems. Typically in terms of additional layers or iterations.. but i like your point and perhaps’n+1’ and ‘1+n’ mean different problem shapes

One fun mechanism I've been using for reducing html size is diffing (with some leniency) pages from same domain to exclude common parts (ie headers/footers). That preprocessing can be useful for any parsing mechanism..

Thanks, will look into it, looks promising

Awesome to hear! Looking forward to a launch -- the Waitlist form was too long to complete, need to take another LLM to fill that :)

Agreed there are several complexities but not sure which ‘this’ you mean - specifically updating selectors is one of the areas I had in mind earlier..

What I'd love to see is scraper builder that uses LLMs/'magic' to generate optimised scraping rules for any page, ie css selectors and processing rules mapped to output keys. So you can run scraping itself at low cost and high performance..

It's "R.I.P.", not "RIP".

Checks calendar… good one! I hope..

Good reminder why not to collect and keep personal data you don’t need

and folding plastic bags into triangles for storage

Can’t imagine that much less unwanted children is anything but net positive though..

Why do we need to meet YC partners to start a startup?

Agreed, it's curious the article never mentions sustainability or benefits of not having uncontrolled population growth, but uses negative language for the trend (collapse, doom, disappearing..)

Clever! With bit of more complexity in generation, you can shave off good number of bytes by using shorter id's, I think?

3 characters per id in base36 should do, in reality even less on average, starting from #0. >100KB reduction?

One could abuse Kotlin to make almost this syntax valid. Something like: states.includes { +”VALID” || +”IN_PROGRESS” }

Where statestype function ‘includes’ takes a lambda that’s run in states context and overrides plus operator for string to evaluate to states.contains(that string). One could, but should they?

No dismissal intended! Was agreeing with you on the premise of a barrage of difficult situations (=‘fires’) in the job. The kinds of challenges you list are to be expected and normal business as usual, but imho doesn’t have to make the role more taxing or difficult than any people-facing corporate job with some accountability. It’s luckily not a boring job either (ymmv, boring = unchallenging). Most situations line or middle manager faces have been solved countless times before, and either have reusable playbooks / mental models to start with, or can benefit from applied common sense and creativity. It’s mostly fun.

The point I badly tried to make was around EMs mental state & health - managing emotional coupling creates space, necessary for the EM to find pragmatic solutions, or workarounds for things far beyond control. (Not that occasionally the problems don’t keep me awake at night, but that was also true for technical challenges as an engineer.)

It’s certainly an unpredictable one, never know what new fires the next week brings, or when they set off a chain reaction pushing the whole team to the brink of despair. Being able to have mental boundaries and (this sounds cold) emotional distance helps a lot!

You’re right - it is not the job for everybody. Perhaps the perverse incentives pushing folks into management for career growth have contributed to lot of human-job misalignment and to this narrative of almost superhuman effort. In what I’ve seen, EM culture tends to keep building that myth up.

Any job is sometimes frustrating, taxing, etc, no argument there either. Big plus one to computers winning on predictability, but humans get the point on autonomy (EM just needs to let go of the idea of telling anyone what they must do). But fundamentally, assuming the personality traits match (a lot is learnable), it is no rocket science, just people.

PS i reread earlier comment and see how it can come off. Not speaking as a engineer who doesn’t understand their manager’s job, but as someone who has been doing it for a decade and managed/mentored/coached number of newer EMs on the way :)

It’s not wrong, but also checklist is not a practical way to approach this job, in my experience.

All the listed activities (and we could list 50 more) are situational and should build to the needs of your job goals. It’s not a hard job and trying to list every detail can be misleadingly overwhelming.

Aim to help people you manage grow, the team be a team, peers be better off than they would be without you, and your company make money or whatever it makes - and you’ll be doing well at the job.

Thank you! Really like Replicache though only used it for hobby projects so far, and enjoyed also the backend side of it (minimal and entirely in supabase stored functions, probably not prod ready). Hope the new approach is a great success for you!

What does this mean for Replicache development, is the client-side codebase mostly shared and can expect continued updates, or more likely to replace the primary focus for you?

The real question is, will it pick up and emulate national archetypes in communication - I expect this model to be introverted and avoid talking to strangers