What performance issues do you usually run into on the current iteration of the app? Just out of personal curiosity so I can take note next time I'm using the application.
OP here - this was a personal collection I had been keeping up to date and decided to make it public given the number of people that have asked me how to get started with VR.
There's a lot going on in the space so if I missed an important resource, would be happy to know.
But people like to pay for convenience, and this is convenient. You pay a monthly fee to receive a predetermined project, all the parts necessary to build it, an entire walk through equipped with videos/photo, and customer support.
Sure the price is inflated (for someone with the know-how) but for people interested in learning electronics, the all-in-one-delivered-monthly is a great sell until you grow out of it.
NotionTheory | http://notiontheory.com/ | Full Stack Engineer | Washington, DC | Remote - Full-Time
We’re a team of talented engineers helping startups deliver their web, mobile, wearable, virtual reality, and hardware products to market in record time. We’re looking to round out our troupe with a full stack developer who can continue to elevate the quality of our web and mobile products for clients.
The web stack typically consists of Ruby on Rails, postgreSQL, and heroku. For the mobile stack, we use Cordova, Ionic framework (built on angularjs), and a firebase or rails server for the backend depending on the project needs.
A deep love for javascript in either stack is a must and you should be comfortable using third party APIs such as stripe, google, twilio, pusher, etc.
Any interest/experience in wearables, virtual reality and hardware/robotics is a plus.
-----
The perks of working at NotionTheory:
- “Take The Time You Need” vacation policy
- “Flex Fridays” - every Friday we work on open source or internal company projects
- Frequent company trips, local events and team activities
NotionTheory | http://notiontheory.com/ | Full Stack Engineer | Washington, DC | Remote - Full-Time
We’re a team of talented engineers helping startups deliver their products to market in record time. We’re looking to round out our troupe with someone who can continue to elevate the quality of our work and relationships with our clients.
The web stack typically consists of Ruby on Rails, postgreSQL, and heroku. For the mobile stack, we use Cordova, Ionic framework (built on angularjs), and a firebase or rails server for the backend depending on the project needs.
A deep love for javascript in either stack is a must and you should be comfortable using third party APIs such as stripe, google, twilio, pusher, etc.
-----
The perks of working at NotionTheory:
- “Take The Time You Need” vacation policy
- “Flex Fridays” - every Friday we work on open source or internal company projects
- Frequent company trips, local events and team activities
We’re a team of talented engineers helping companies rapidly build and deliver their products to market in just 4 - 6 weeks. We're looking to round out our team with someone who can continue to help elevate the quality of our work and relationships with our clients.
As part of the core team, you’ll be expected to help play the role of stand-in CTO to our clients.
In addition to being a kickass developer, you should also:
- Have a track record of developing and delivering products to market (while maintaining quality)
- Have a sense of product ownership and bring innovative ideas to the table for our company and our clients
- Not be afraid to say “I don’t know”. You routinely figure things out.
- Be seriously committed to helping build a startup, even though things won’t always be easy.
- Have an insatiable thirst to always be learning and experimenting
Began a startup senior year of college (Thryv). Managed to build a team, get sales, generate revenue and score a large partnership. Long story short, I was a customer of my own product and assumed I knew what other customers wanted. I spent the next 6 months having a product built without validating my initial assumptions before launching. The product was too niche only fitting customers who had my specific workflow and I ultimately found this out too late when we ran out of steam/resources. Total timeline (including fuckups) was 3 years.
I was non-technical at my first startup (domain expert & business/marketing/sales) and after I shut it down, I spent the next 8 months teaching myself how to build software programs, becoming a now tech co-founder.
I then started my second startup (http://notiontheory.com/) by getting $20k pre-sales in 2 weeks to validate my idea before committing to it.
Attempt 2 has been far more successful and we're already beginning hiring in month 5 bootstrapped.
The process is the same for converting doge to USD (which I should make clear in the guide, thanks).
There are a few exchanges with plans to offer direct exchange from Doge to USD in the coming weeks, which I will also be making a guide for when it's released.
You could alternatively sell your Doge for USD through a service like eBay and add a nice markup for convenience (doge is selling for 2x the value in some bids), although you chance dealing with scammers.
edit* thanks for the props, specifically in comic sans :)
When you're using an offline wallet like bitcoin-qt or dogecoin-qt, you have to download the entire blockchain for the cryptocurrency. This is what's 'syncing' and can take a while to finish.
You can bypass having to download the blockchain by using an online wallet instead, which solves that specific pain point but they're less secure than your local storage offline wallet.
Just thinking out loud but if I went on a hiking trip with a couple of friends and we all wanted to show off an album of pictures to other, it makes sense I would give a view-only link to people who wanted to view the album and an edit link to those who came on the trip to contribute photos.
It could be something as simple as selecting "Yes" generates an edit var with the associated link. If someone pastes the edit URL into their browser and the edit var = the album id, allow edit. Else force view only.
Edit* This is just an opinion and what logically makes sense to me. Would love to hear what others think.
Simple, useful, great UI and best of all no account required.
Awesome job.
Only question is regarding the switch between view-only and collaborative. When I choose to allow friends to contribute to the album, the provided link doesn't change.
I assume you have a view-only link and an edit link that is passed a var to allow people to modify it. How does this work in your application?