Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

When deployments are easy, code becomes simpler

bitbytebit.substack.com

Post reply on HN
Print view View original

121–124 of 124 posts

Re: When deployments are easy, code becomes simpler

#121

Post by chaxor »

baq wrote: post #57
chaxor wrote: post #31

Earlier quoted context omitted.

If a git commit hash was directly tied to a data hash at that state (IPFS), that would be trivial.

And useless. Unless customers don’t care about their data.

I don't understand your statement. If a git clone of a specific commit also pulls the data that is generated from that commit hash via IPFS simultaneously, then you can always have the data at whatever state you choose. How might this have a negative effect on conserving the data? Do you mean that there are additional structures required to manage keys if the data is encrypted?

Re: When deployments are easy, code becomes simpler

#122

Post by chaxor »

tbrownaw wrote: post #40
chaxor wrote: post #31

Earlier quoted context omitted.

If a git commit hash was directly tied to a data hash at that state (IPFS), that would be trivial.

Or have the SAN make a snapshot of your db before the deploy, no fancy solution-looking-for-a-problem tech needed. Completely reverting all the state to some point in the past is easy and have been a solved problem for quite a while. The actual problem is undoing states changes related to the code change, while not losing state changes related to normal system activity. If I add some new fields to how my web forum re…

Good point, this system is much more useful for scientists and ML researchers, etc. wherein the code may generate datasets over several weeks or months of compute time, but produce some output that should be directly tied to the code.

You're right though. Systems in the social media space dealing with users appending to a database typically don't have this requirement to be easily reproducible, so the local snapshots are the right choice.

Re: When deployments are easy, code becomes simpler

#123

Post by ajkjk »

nicoburns wrote: post #113
ajkjk wrote: post #28

Earlier quoted context omitted.

Strongly disagree this is a junior dev thing. Most of the terribly complex abstractions are, in my experience creates by people who have enough seniority that others can't easily question them. There are good devs and bad devs, and there are junior and senior devs, but it's the first axis that determines code quality.

Hmmm… well it certainly was for me. My code has gotten a lot simpler over time!

Well no doubt! Same. You can certainly get better at programming as you get more experience. I'm just saying: the axis that determines this stuff is skill, not seniority. They correlate but they're not the same thing.
Post reply on HN