what about...
• freelancer • advisor • fractional cto • performance consultant • various other vendors
101 karma · joined October 4, 2011
www.iheavy.com/blog/
• freelancer • advisor • fractional cto • performance consultant • various other vendors
30 questions to ask a serverless fanboy http://www.iheavy.com/2017/03/13/30-questions-to-ask-a-serve....
The more general truth is quality does not correlate with cost.
Google Rory Sutherlands TED talk
As others have said, honing your ideas is also a process that blogging chisels & fine tunes.
http://www.iheavy.com/2017/03/13/30-questions-to-ask-a-serve...
o Whatever you may feel always be polite with reminders. Do not make them angry or make accusations. It sounds like they're already in a frustrating position.
o remember they have a legal obligation to meet payroll. Next on the list is lights on, heat & rent. After that hosting bill. And then below all of these are vendors. Hopefully you are at the top of the vendor list!
o if they run out of money you may not get paid. That's how it works!
o over the years I only had this happen once. It was $9k, but I subsequently got 2k of that. Still every month like clock work I send "a gentle reminder" of outstanding invoice for $7k. They still respond. So I know if that situation changes in the future I'll be first in line to get paid.
Need to build a monitor or component to handle missing on delete cascade records.
MySQL & Postgres carry some of those same attributes. Even though they are user processes and the OS controls the lower levels, you would typically deploy them on their own servers, and give them all the memory & disk I/O you could, because they were their own operating systems essentially.
It's not clear to me how building a database "like an operating system" is something new. What I did see new in there was a consistency checking tool. That is super important. Because in a distributed environment you're bound to have drift.
Also I'd like to see how they managed to get full ACID Compliance. Fast network interfaces are great but there is still some latency which means hiccups when multiple nodes try to update the same row.
Checking emails after hours? Include that. Thinking through problems in the shower? Include that time too. Maintenance at 2am Saturday night? Incl that x2.
If the number seems small bc you're working 60 real hours a week, then think again.
Trying to factor in stock? When it comes to investing warren buffet says go for the s&p 500!
Devs to create change, new features & build product to meet customer needs.
Ops to resist change. To provide a rate limit. And a sense of perspective. Bc they're tasked with stability & continuity.
Maybe Neil Stephenson is right, that Linux tells the Gilgamesh story of hacker culture
http://www.iheavy.com/2015/10/28/linux-command-line-stephens...