HN user

googletron

2,956 karma
Posts136
Comments220
View on HN
www.mahdiyusuf.com 1mo ago

Looping Casino

googletron
2pts0
mahdiyusuf.com 5mo ago

Agent is building things you'll never use

googletron
6pts1
mahdiyusuf.com 6mo ago

Why your coding agent keeps undoing your architecture

googletron
2pts1
mahdiyusuf.com 10mo ago

So You Want to Host Your Own LLM? Don't

googletron
2pts3
architecturenotes.co 4y ago

Fallacies of distributed systems

googletron
224pts60
info.crunchydata.com 5y ago

Cleaning Up Your Postgres Database

googletron
6pts0
mahdiyusuf.com 5y ago

How I got an a6000 for under 300 bucks!

googletron
1pts0
mahdiyusuf.com 5y ago

I discovered I was a baseball card “investor” for 30 years

googletron
1pts0
mahdiyusuf.com 5y ago

Year(Decade) of the Homelab

googletron
4pts0
movesimporter.com 8y ago

Moves Gyroscope

googletron
1pts0
github.com 8y ago

Awesome Siri Shortcuts

googletron
4pts0
github.com 8y ago

Apple/Siri Shortcuts Repository

googletron
2pts0
developer.okta.com 8y ago

What Happens If Your JWT Is Stolen?

googletron
4pts0
blog.gyrosco.pe 8y ago

A year of building Gyroscope

googletron
4pts0
blog.gyrosco.pe 8y ago

Building the Gyroscope Annual Reports

googletron
3pts0
blog.gyrosco.pe 8y ago

How Gyroscope Detects Your Sleep

googletron
10pts1
tincture.io 9y ago

Wearables are expensive

googletron
2pts0
techcrunch.com 9y ago

Gyroscope is building the back end to the journey of you

googletron
2pts0
neckbeardrepublic.com 9y ago

Free Python Videos for Beginners to Intermediates

googletron
2pts0
blog.gyrosco.pe 9y ago

Task Manager for Your Body

googletron
2pts0
mahdiyusuf.com 9y ago

Fasting and Programming

googletron
27pts9
blog.gyrosco.pe 9y ago

10 principles for smooth web animations

googletron
4pts0
gyrosco.pe 9y ago

Gyroscope for Chrome

googletron
5pts0
tumblr.github.io 9y ago

Apple Live Photo Support on the Web

googletron
2pts0
blog.gyrosco.pe 9y ago

How to keep your HealthKit data

googletron
3pts0
blog.gyrosco.pe 9y ago

The Potential Future of Apple Watch

googletron
6pts0
blog.gyrosco.pe 10y ago

Gyroscope Profile: How a heart attack at 38 turned my life around

googletron
5pts0
blog.gyrosco.pe 10y ago

Building the Gyroscope App with React Native

googletron
100pts22
blog.gyrosco.pe 10y ago

Monitor Your Life Like You Would a Server

googletron
2pts0
gyrosco.pe 10y ago

Gyroscope Annual Report 2015

googletron
18pts5
Redis explained 4 years ago

I would ensure that the data size is managed if you hit the limits due to your policy Redis will stop responding to ensure the data it has isn’t lost. I would also turn on some sort of persistence for data recovery in case of catastrophic failure. Early on this is totally fine and I would setup some monitors in redis data size relative to memory and try to keep 20% overhead weird things start to happen when systems are memory constrained.

Redis explained 4 years ago

understanding the big-O complexity of each operation (…and ensuring that none of your interactions are more than logarithmic).

This is a good idea, maybe a prompt for another post.

Redis explained 4 years ago

My personal nightmare happened and accidentally published a rough draft! It has since been updated! Apologies!

Redis explained 4 years ago

I wrote a little post on how Redis works and its various setups! How does everyone setup Redis? Elasticache is a good answer too :P

You are absolutely right about the C being more inline with CAP one.

I have a post in draft to discuss disk trade offs which digs into this aspect, its impossible to dig into everything in this level of a post.

Good point. Its often the problem space and other constraints that usually drive these decisions. Its important that you deal with problems when you have them.