1,282 karma · joined April 4, 2013
email: katzke at gmail; twitter: kkatzke
All of the concern about the 'failure' is a matter of loss of control of water release, not of breach of the main dam structure.
* - via electronic means only
The approach done by spacebuckets isn't very efficient. I haven't looked at the site recently and it currently seems to have been hugged to death, but LEDs have a dramatically lower energy consumption compared to individual CFLs, especially if you use one converter and run them all on the same DC circuit.
There are also parts of the world where you could run this concept economically using solar panels to provide greens that are normally impossible to grow out of season without the added cost of transportation. (You would also have to cool the building, of course, but that can also be done in a carbon neutral fashion.)
I have very very little experience with electrical engineering (I'm in the Lego mindset of I plug things in according to things I find online until they work), but is there something I should be using instead with 120V ~3-5 A loads?
I can do this because no one else is around when I'm working or I can close the door and be alone. The main reason that I don't use something with a headset is because I always had problems with headsets, especially wireless ones -- either they wouldn't pair, or they'd come unpaired between calls and I'd have to do the "can you hear me" dance, or I'd have something wired on my head and it'd be a pain in the butt, or ... well, the list goes on.
If you have something wireless, make sure you know how to use it really well and that you have a test or two that you can quickly do to ensure operation and that you have a backup you can quickly fail over to.
I spent four years working remote in a 24/7 operations position, and then another few years working out of a satellite office but from home at night in a similar position. Some of the marathon troubleshooting calls I was on would exhaust even the most serious of batteries.
I have a degree in logistics, but I work as a scripting-heavy systems engineer. My hobby is home construction, especially building systems like drainage planes, vapor management in walls, and structured wiring and plumbing. It's literally all the same thing with almost identical sets of problems.
I interviewed there for a Systems Administrator position. Part of the interview was a code sample -- solve a specific problem using a scripting language. I submitted a 'mvp' -- a script that worked well, took about an hour of effort, and performed the required task in two environments, one of which was a chrooted jail that the person who graded it was welcome to log in to just in case the code did not work on their workstation.
The feedback from the examiner relayed via the HR recruiter was that it was the "worst code they had ever seen," and they were offended that I did not write it in an object oriented manner and that it completely lacked any testing and validation -- which was wrong, actually, I validated inputs with a regular expression.
Remember, this was for a systems administrator position, not a developer position.
And after that feedback, I didn't want to work for Wikimedia anymore.
But companies want me to be REALLY EXCITED like I could always get in my 20s. I just can't get that excited anymore; it takes too much extra energy that I'd rather conserve for doing real work that matters to me.
It ended up being three weeks before we agreed that I'd successfully handed off everything.
No bad feelings either way -- I'd joined the company because they had said that they wanted to 'grow up,' but that was a feeling percolating up from below. The lower levels of the company wanted to grow up and stop firefighting all the time. The top levels of the company would fight you every last way.
"As far as I can tell, what happens at these companies is that they started by concentrating almost totally on product growth. That’s completely and totally reasonable, because companies are worth approximately zero when they’re founded; they don’t bother with things that protect them from losses, like good ops practices or actually having security, because there’s nothing to lose.
The result is a culture where people are hyper-focused on growth and ignore risk. That culture tends to stick even after company has grown to be worth well over a billion dollars, and the companies have something to lose. Anyone who comes into one of these companies from Google, Amazon, or another place with solid ops practices is shocked. Often, they try to fix things, and then leave when they can’t make a dent."
He wanted to offer non-predatory lower interest loans to higher risk clients, in concert with banking services that are difficult to provide to higher risk immigrant clients like checking and savings accounts and debit cards.
But the NCUA wouldn't allow him to set interest rates lower or offer checking/debit accounts.
> Now obviously this is a blatant transgression — absolute, unequivocal application of Taylorist management in the context of a Product Development mindset
From the Wikipedia article that HE LINKS, this caveat is given as to why Taylorist principles still sometimes apply:
> Although scientific management as a distinct theory or school of thought was obsolete by the 1930s, most of its themes are still important parts of industrial engineering and management today. These include analysis; synthesis; logic; rationality; empiricism; work ethic; efficiency and elimination of waste; standardization of best practices.
And that's what JIRA is used for in most companies.
Luckily, I can still program. I didn't loose much mental capacity. But there's a thing in the chronic pain support community called the 'theory of spoons.' In short, you get a certain number of spoons when you wake up in the morning. Some days it's more, some days it's less. You give a spoon out for everything you do and every interaction you have. Most days, you'll run out of spoons midway through the day through normal interaction. But when you run out of spoons, you have nothing to stop yourself from just hurting. You don't have anything to give yourself to stop the pain, much less to give to anyone else to make them feel needed in the relationship you have, to make them feel valued at work, to make them feel happy or welcome to be in your home, to produce something awesome on your side project, to make a healthy dinner ... there just aren't enough spoons on any given day. But the worst part is that you end up in physical pain because you've given out all your spoons, and you know that the people around you are hurting emotionally because you don't have any spoons to give them.
Most people eventually learn to budget their spoons carefully. If you're SUPER cautious about it and you put many of your ambitions aside, you can get to a point where you still have a spoon left by the time you get home at night. But it means you're probably not going to be an astronaut, and you probably are very shallowly involved with your community, and you probably aren't going to leave much of a mark on the world outside of the people who love you. Recognizing that early in life is pretty important so that you do have people who love you.
To me, this sounds like "As founder, I had access to all of Homejoy's data, so I just took it with me."
More experienced people tend to see the value in growing well AND fast at the same time. So more experienced engineers (aka, older folks) tend to always push away from the cheap and towards the fast/good side of the line ... or if cheap is a mandate, then they push towards the good/cheap side of the line.
None of that is what YC is about.
For instance, "More experienced people are likely to look down their nose at company culture" doesn't really have a comparison with any other protected class.