HN user

onefuncman

184 karma
Posts0
Comments131
View on HN
No posts found.

conceptual meaning consistent across all accounts.

Except programmers quite often get the conceptual meaning wrong and incorrectly generalize further. Credit and debit just mean increase or decrease in account balance. You cannot know how it affects liabilities or assets without knowing what type of account is being modified.

When an account is CREDITED, this always represents an increase in liabilities[0] (or equivalently, a decrease in assets).

When an account is DEBITED, this always represents an increase in assets (or equivalently, a decrease in liabilities).

This is where you're wrong. You can credit and debit Accounts Payable and Accounts Receivable. If you credit AP, you're increasing liability, if you credit AR, you're increasing assets.

Botspam apocalypse 4 years ago

I want to run a honeypot for doing more research on bots and the economics for them, but I get bogged down quickly in the planning stages. I should just start with a vulnerable wordpress site or something.

I go back and forth between doing this on a daily or weekly cadence, but it's also the only thing I've found to keep being useful over time. I always get a wild hair to try and write Markdown or something but really I just end up writing text and it's fine. The most meta I ever get is adding additional keywords for me to search later.

I used Gource to visualize a hackathon, we had everyone start from a templated repo so it was really easy to show the entirety of participants coding activity (albeit at a macro level)

I put my 1Password vault on Dropbox specifically because I can install both apps via iOS store on a new phone and bootstrap my setup with just 2 passwords.

iCloud is actually too hard to recover in case of hardware loss, I don't recommend it to anyone.

At the first sign of any pain I try to identify the cause. It's almost always ergonomic related.

The most useful stretch/exercise I do is pushing my hands together, palms flat against each other, in front of my sternum with my fingers pointing up, out, and down for ~30 seconds in each position, once or twice a day.

Slack is down 6 years ago

It's easy to fall behind on bumping up the high watermark for your max autoscaling or for new traffic patterns to cause emergent instability. New code paths are taking unprecedented amounts of traffic all the time.

In 2021, how does one keep track of resource starvation at the process, container, os, service, pod, cluster, availability zone and region levels?

the adage from service level perf testing (you don't know what's really slow/brittle until you measure...) holds equally well at the systems level. Yes, you can probably identify decent areas to improve by guessing, but you'll never find your blind spots...

this isn't any different than microservices getting a deathball dependency on a user service or logging service or security service or ...

you either don't allow microservices to consume from others' topics, or you publish event schemas so they can still iterate independently.

the move to a 2nd kafka cluster in my experience has always been driven by isolation and fault tolerance concerns, not scalability.