This is a great idea. I could see becoming a customer of yours if you added:
- payment in USD
- Ability to provide a post-receive hook to run validation / tests / benchmarks, and see results with the notification of submission. I appreciate that doing this in secure fashion is a nontrivial effort.
Thanks! Webhooks to implement that kind of post-receive functionality are on the TODO list. If you like, get in touch at hello@takehome.io and I'll let you know once they're done.
Honest question: why? Can't your card / bank / PayPal do the conversion for you? (I say this as a Canadian who often pays USD with my Canadian card / bank account).
The bigger issue for me is pricing in USD, and less about the currency in which payment is collected. I'm in the UK, and while I can generally work out a rough exchange rate for GBP to USD and EUR in my head, I've no idea what the current AUD rate is. Making me check is a small but real barrier.
This is a rare case where it seems useful for me to externalize my inner monologue: "Well, this just looks like Jupyter lite... oh, wait, this is Mike Bostock's project? He's built some very cool visualizations and some really powerful libraries with a tasteful API design... if this is his idea of a useful workflow it's probably well thought-out and executed and worth checking out."
Seconded, big time. Blockchain was a hand-wavy haze for me until I got my hands on this book. As a programmer it's frustrating to read most high-level summaries of cryptocurrency/blockchain because they are often geared to a general audience and raise more technical questions than they answer - not so in "Mastering Bitcoin." The author does an impressive job of creating motivating scenarios before diving into concrete details. The chapters are well-sequenced but they stand up well to a bit of jumping around as your curiosity takes you in different directions. I thought this book was a real pedagogical achievement.
I'm looking forward to his book on Ethereum. In the meantime, Chris Dannen's "Introducing Ethereum and Solidity" is helping me to get a good grasp.
I love this book for how approachable, readable, and even enjoyable it is. Skiena does a great job of motivating each of the algorithmic techniques. I recommend this one widely.
Then you are absolutely going to hate the article I recently contributed to Gopher Academy's advent series, https://blog.gopheracademy.com/advent-2016/go-syntax-for-dsl... , about using Go to create terse, declarative DSLs for things like, say, building a webapp.
Stabby! Several thumbs up to the point #1, that interface boundaries needn't be coincident with service boundaries. In my experience, the benefit of breaking out microservices is the decoupled deployment. A heuristic is, if you have fixes/features that are waiting to be pushed to production until unrelated code is passing/QA'd, you've got a good candidate for a separate service.
I think this is good advice- risk management is important in managing your own career. It's easy to get complacent with recruiter outreach hitting your InMail at a steady clip but macro, micro, exogenous, endogenous factors can shift your short-to-medium term career prospects significantly.
"Casual" being the operative term here. Nixon et al had plenty to say behind closed doors that at least for the last generation or two, would not be tolerated by the decent voting public from a mainstream candidate with any hope of being elected. Trump is not only saying these things in public, on the record, but he's campaigning on them. He's a leader in misogyny and bigotry.
