25k per unit, assuming the battery lasts 5 years, is uneconomically high at $5k/year per home.
A 100kw generator can produce enough power for 100 homes, costs ~$50k all in, and ~$1k per day in fuel costs to run during an outage. Assuming the generator also lasts 5 years, that's only $100/year per home, 50x less than the battery solution.
Batteries are for the foreseeable future way too expensive.
No. Companies just have to re-hire fired employees and pay lost wages and benefits. IMO Starbucks should pay a large punitive fine that gets split between the fired workers and the NLRB.
I've never seen anyone directly make this case. Most people seem to want their colleagues (many of whom are friends) to keep their jobs more than they want the stock price to go up.
I'm still not convinced VSCode is faster and better. My Atom setup was never slow, the only thing that wasn't instantaneous was code completion. For me, it felt like VSCode came out of nowhere and surpassed Atom for inexplicable reasons.
Twitter won't die, but it won't make much of a profit either. Elon Musk will find another buyer in 2 years for $25 billion and make most of his money back while leaving the company saddled with most of the $11 billion in debt financing.
These tools are amazing for prototyping. I had an idea for a promotional poster, and seeing my idea just by writing it felt like magic. The generated image had too many artifacts to use, but gave me a guideline to follow when creating the real thing in Pixlr.
AI content generation (text, image, source code, video, music) will be a huge boon for prototyping where applied judiciously.
I had the luck of getting to interact with Simon a little at my first real programmer job at Eventbrite. You would never know meeting him that he was one of the creators of Django, (and TIL querySelector!). He was infectiously curious and excited about programming in a way that bubbled over to most people he interacted with. He would also enthusiastically engage with what you were working on, even the beginner project I had at the time. I don't know him well, but my impression was not just of a great programmer, but a great colleague and an authentically positive person.
I used Atom for a long time after it was cool. I just loved the idea of an editor I could extend using the standard web tools and frameworks. Overall love this project, and still am a little miffed that VSCode ate their lunch. Best of luck on everything Nathan and the team do.
Thanks for acknowledging how much harder this is when you use a cloud-specific feature. Modifying your codebase to migrate off some cloud specific service seems like it would be by far the hardest part of switching clouds.
Even though this begins with a pitch for empowering tenants, the customers are the landlords. The value for landlords comes at the expense of tenants in several ways.
* It prevents tenants who don't meet income or other requirements from even looking at the unit.
* It makes tenants liable for noting damage as soon as they view a unit to avoid it being attributed to them, a daunting task.
* And it removes a face to face interaction that forces some accountability on landlords who don't provide a clean/cared for unit.
Notably absent is a mechanism for tenants to provide feedback to landlords on the listing. The Questions feature is helpful, but not designed for concerns/praise.
I used d3.js for one of my first programming projects. I was grateful and impressed that almost every question on Stack Overflow was answered by Mike Bostock or Jason Davies.
I'm (a little) older and (a little) wiser, and know this kind of support is a huge amount of work. It sounds like
"focus[ing] on learning and broadening your perspective" is what fueled all those answers I so appreciated.
One trick of `pragma journal_mode = WAL` is that even with synchronous normal, SQLite syncs when you close the last connection [1]. So re-using a connection is key to getting the full benefits if you're executing commands from a single thread/process.
This list is self-consciously blunt/rude (correlating programming practices with intelligence and sanity) and unaccountable ("who knows what I'll believe in a few more years"). It's an annoying combination. I imagine many reader will haughtily deploy these commandments against their colleagues.
Going from a local db to one over a network has at least one risk. The SQLite docs gives developers the okay to write "n+1" style queries (https://www.sqlite.org/np1queryprob.html). When the db is on the same file system as the application this pattern is fine. But as soon a you add a network call it becomes a potential bottleneck.
A 100kw generator can produce enough power for 100 homes, costs ~$50k all in, and ~$1k per day in fuel costs to run during an outage. Assuming the generator also lasts 5 years, that's only $100/year per home, 50x less than the battery solution.
Batteries are for the foreseeable future way too expensive.