107 karma · joined February 14, 2011
I record sounds with a Shure MV88+ stereo condenser microphone connected to an iPhone. I airdrop the WAV files to a MacBook Pro, where a python script normalizes the audio to a loudness level of -14 LUFS with a level of -1 dBTP (dB True Peak ), generates an HD video, and posts it to YouTube. I'm just getting started. It's more of a hobby than a hustle.
Would be interested to hear about some of these.
My desk is also somewhat home made and doubles as my hobby project studio for song writing and recording. Behind my chair (not visible in the pic.) are a 10" sub woofer and a larger white board. I have a tiny bike mirror over my right monitor to avoid a bad shock when someone stops by my desk while I'm deep in a project. The tiny red button on the left corner of my desk is to engage/disengage the sub woofer. Most days my dog sleeps on the rug by my chair and amazingly I have never rolled over him.
My desk: http://i.imgur.com/OfYjTgX.jpg Her desk: http://i.imgur.com/vI4GR7H.jpg
I understand having secondary name servers and switching application IPs, but (pardon my ignorance) how does an web application host or website achieve high availability in this scenario?
What I have learned:
- Try to think about/plan for ten years out - Make your application easy/pleasant/fun to use for you and your customers - Limit third party dependencies at all junctures - Log everything, it makes support and monitoring easy and fast - Customers don't care what language/platform/db you use - Have a support ticket system - Have a coding convention/style and stick to it - Life work balance is important, take vacations - Run lots of backups - Keep it simple and thank yourself later!
Of course YMMV. Hope that's helpful to someone starting out.
You're are coding on a small planet orbiting a small star that will burn out in a few billion years, taking your planet and all of your code with it.
Is it really of any universal consequence if you're producing VB6 during business hours or building a disappearing <whatever> app at an overnight hackathon?
I think not. Code on dark matter developers, wherever the hell you are.
I like the idea of a human UUID/GUID type identifier.
I would also like to think that this is solvable using strictly biological and physical properties, sampled at birth.
Otherwise, time and culture factors would seem make it difficult to produce a static set of "apples to apples" questions and answers.
I wonder if the right maths applied to existing genetic and forensics big data sets could produce the 33 questions.
A free saas + iaas cloud platform that provides all the plumbing and infrastructure necessary to launch your startup in 90 days ...or else.
If your startup doesn't achieve exit or real revenue target within 90 days, you forfeit ownership to Snapco.
Else, Snapco takes a percent of exit proceeds and ongoing revenue.
</kidding>
We try to detect/filter them in the sales process. Unfortunately saying "I don't thing our product is a good fit for you" invariably seems to make them want it even more.
- Apartments - Autos - Boats - Cars - Forsale - Homes - Motorcycles - Rent - Yachts
I wonder what percent of US GDP sales of those products represent.