kespindler
It's a crypto yield account that downplays the fact that it's crypto.
Do with that knowledge what you want.
Write up or copy a few page doc outlining security best practices, then require every employee to read & sign an acknowledgement that they've read it. Now every employee has gone through security training.
Add these two lines to the top to use node executables and load the dotenv:
``` set dotenv-load := true export PATH := "./node_modules/.bin:" + env_var('PATH') ```
I'm currently building a network of domain expert mentors, where companies can connect with experts for advising their existing team to solve business problems. Think of it like very low commitment consulting. It might be a great way to get a better feel for industry (and the salary you can command) before making a hard commitment.
If that sounds interesting, shoot me an email. My email is <my username> at gmail dot com.
1. Don't use MongoDB.
2. Don't use high level ORMs. Stay (reasonably) close to SQL. And yes, it should be SQL. Almost certainly Postgres.
3. Especially don't use Mongoid.
It has two chapters that are especially relevant for you: "Chapter 2: Transform self-love into empathy: The law of narcissism", which might be self-evident in its value from the title, and "Chapter 4: Determine the strength of people's character: The law of compulsive behavior", which discusses toxic personality types, how to avoid them, and what to do in case you notice those patterns in your own behavior. I think you'll find both of those chapters extremely illuminating.
The whole book is worth checking out too. And a relationship with a good executive coach or therapist works wonders too!
1. Get some kind of market validation before you build. Get commitments from paying customers (or even pre-payment), or directly see them paying for a near-identical offering, and have a competitive advantage to deliver it more cheaply.
2. Do an inventory exercise of why these projects have failed. Doing a quick run-through, it looks like you didn't do marketing or user research for any of these projects. If making a side business still excites you, make sure you do these steps before going to build any future side business.
3. I know nothing about landscaping, but as an outsider, Bloom looks a promising product. Go talk to customers!
3. If the marketing side of things doesn't interest you, but you still want to make side money, reach out to me, my email is <hn username> at gmail. My background is pure engineering, but I have friends who are looking for technical co-founders and have ideas that I could use more technical talent on.
See the gender ratio of Facebook events
For more info, check out 4H work week, Lean Startup, or http://firstround.com/review/90-of-feedback-is-crap-how-to-f...
Show HN: Modern Python3 web framework
The business solution here is very clever. As an engineer, my instinct is to fully automate any system. Clara is a great example where the most effective answer is getting the 90% solution, then going the last mile with humans to bring it up to 99% (making that up) accuracy, with most of the same savings. Imagine similar solutions for customer support (especially over website chat bars. Some systems like this already exist.)
Albatross: dead simple async python3 web framework
The Golden Handcuffs Are Tighter Than You Think
The secret sauce to Uber's Growth
The Future
github.com/kespindler/puffin
Instead of learning a new language and new syntax, just use python!
Puffin - A Python awk replacement
edit: realize don't think there is pming here. i'm my username at gmail on e-mail.
Striking Out On Your Own
Feedback Wanted on Python Build System
After being a bit frustrated with both command line tools such as Fabric as well as build utilities like SCons, I thought I'd spend a bit of time thinking about what would make an awesome build utility for Python. I modeled a lot of it after Rake, due to its immense popularity. However, I distinctly tried to make things more explicit and more Pythonic. I created an example script that would be...
I'm also going to disagree with what the author says. I go to an ivy-league school, and there are two things that make all the difference: the caliber of students, and the atmosphere of hard work. Of course there are smart people at every school, as Author writes in describing Honors programs. But the concentration is just incredibly high at Ivys. Any random person you run into or work with is most likely brilliant in some way or other.
Atmosphere of hard work - Being surrounded by many high-achievers, you just can't help but push yourself to work harder, achieve more, etc. As long as you're in touch with yourself to avoid burnout, I love this atmosphere because it pushes me to accomplish more than I would were I surrounded by a bunch of people who just want to drink all day every day (of course there are those students, but they're in the minority.)
That's not to say an Ivy is always worth it. Rather, I think you can't make a blanket statement about whether it's appropriate or not. For some it will be, for some it won't be.