4 ms·
As someone that wears far too many hats to the point of daily paralysis, these don't sound too intimdating... until I need to figure out what to do first. This
by devonkim 13y ago
As someone that wears far too many hats to the point of daily paralysis, these don't sound too intimdating... until I need to figure out what to do first. This is what iterative anything / MVP / lean startup thinking is for and also determines what I think the biggest difference between effective and ineffective people are - prioritization during execution.
- Deploying? I do integrations and devops-like stuff at work, and online discussions tend to overblow this topic given this probably matters among the least. The "correct" way is the fastest that will get the job done now so you can keep your momentum going. Until you go full hog hot-deploying to keep your uptime high, expect to destroy everything eventually, who cares if it's sloppy if it went into the trash? Just git receive hooks are good enough for toy projects like O(n^3) algorithms are probably fine for starting some random webapp.
-Business models are in abundant supply out given the number of times "ideas people" that "just need someone to make an app/site of it" have approached me. Unless you're undertaking significant costs or are on the edge of financial ruin, you shouldn't worry though given starting a tech company is the cheapest it's ever been and only getting cheaper (per Mark Cuban). However, you may want to do some quick market research so you don't waste too much time building something that nobody wants - your time is actually going up in cost at a rate faster than Moore's Law gives you savings! On the other hand, don't be like me and think that focus groups and all the stuff that big companies do for thousands typically for a waste of money applies for you. It seems common sense but we all do dumb things in hindsight and it can be hard to step outside your box. People with good prioritization skills do less dumb things wrt execution, that much I can assure you.
- Taxes are pretty simple for tiny companies in the US (this IS still a cheap place to run a business comparatively), you can probably hire an accountant to do it for a couple hundred bucks without paying a lawyer for even more. Everyone gets moved to Delaware or something later, just get that done hastily to check it off. It's the FUNDING that will make your head spin, taxes are trivial in comparison. Beyond that it's all good problems to have from everything I've read.
For me, I honestly think the hardest part is coming up with a coding project that keeps me motivated long enough without encountering some real hard blocks that just can't scale even though I know they're stupid easy for others. I get a small aneurysm having to deal with frontend design decisions & execution as a systems & backend stack guy primarily. Font choices, picking color palettes for an audience, ... am I making a business or planning my wedding again?
I've only shipped maybe a couple personal projects for the public to see though, so perhaps I'm full of crap and I wasted everyone's time. But if anything, I know how my own habits lead to ineffective output even with what seems like a lot of effort, so I think by telling people the opposite of what I do, it would give better results for others than saying what I actually do.