Shyp is using a combination of technology, logistics, and outstanding customer service to make it easy for people and businesses to send things to each other.
We're hiring several important engineering roles: API engineers, DevOps and QA. Of note, especially looking for talented Devops folks that have had experience with Linux, AWS and Docker.
We've got a lot of exciting problems to solve, and we're still a small team - the opportunity to take on a big role and have huge impact is very real.
You raise a great point and honestly my two hypothesis are
1) People would realize that its very valuable to get the opinions of strangers before "wasting" time creating something they think they might want. One could argue that talk is cheap but I'm sure this guidance can lead to very valuable results maybe rethinking the idea or whatever the case.
2) You don't need domain experts in the beginning per se, just a bunch of minds who can quickly determine if they would use or not use a service. The motivation behind domain experts joining in the future might be just to help and give back to the entrepreneurial community (I admit this last point is kinda corny lol)
really great feedback thanks. I'm just thinking of a quick way to get that idea to a diverse group of teachers ( for example ) and get feedback in real time as opposed to just the ones I know who are likely to just say "yeah we'd use it" so they can make me happy.
I was thinking of creating a service where you can blast out an idea. If enough people signup and maybe categorize themselves, you can possibly get valuable feedback on whatever idea you just had. What do you think?
i think this is a pretty interesting way of validating but it involves spending some money which most people might not have. I was thinking more about the "out of the shower" aha moments where you really just want to get instant fly-or-die feedback...is it valuable to just go ahead a build an MVP or really try and talk to people about it to see if theres a need (although talk is really cheap, hence the need for an MVP)
Hey! am actually in the same position as you are. I think I have a good idea but I can come up with a million reasons why i'm not developing e.g. being in school taking 7 classes, studying for the GRE being in debt bla bla bla.
Anyways, to remedy this, it was pretty much just a basic decision. I told myself that I'm wallowing in self pity about problems and not doing anything about it. I decided to act now.
This is not enough though, I think it's important to hold yourself accountable to someone. Maybe get invovled in a startup competetion that requires an update every week, tell a close friend about the idea ( this helps to validate it maybe, and they might keep asking you about it forcing you to build it). Set minimal goals (like oh, i'm going to get my login system working today). And just start building.
Products really just start out as features. If you can implement just one simple feature, you'll be well on your way. And don't be afraid, just be the man in the arena http://www.theodore-roosevelt.com/trsorbonnespeech.html I hope this helps.
PS - Stop reading too many blogs and news and stuff! Just build..I know I always get carried away by tech news instead of being the news
haha, yeah i think so too. But they might add some features maybe integrate with instagram (if they dont have that already--I dunno) that might still give em an advantage...
But I don't think twitter is dependent on third party apps. I just feel that as an organization you can't necessarily think about and implement every single permutation of features that can be created with your data. Obviously it's your data and you reserve the right to release or not release it as you please.
Thanks for pointing out my erroneous assumption though. I just thought that if there are restrictions to what you can create and twitter obviously would keep adding new features to the product, it's not enough incentive for you as a developer to create twitter clients.
But like you clearly pointed out, their most lucrative users might not really care about them. We agree to disagree
i'm not necessarily talking about any specific apps per se. My understanding of their rule is that you cannot create third party apps that mimic the twitter user experience. Now this experience is going to involve photo-sharing which developers might have spent a long time creating but now might not be able to continue work on it.
I'm also concerned about what other features they might create that might infringe upon what a developer thought at the time was not a direct user experience on twitter...
In the end, I'm more interested in seeing how it all plays out. I like twitter and I'm pretty sure developers will continue to find innovative ways of using their rich data
couldnt agree more. It kinda reminds me about open source and how the power of many is greater than one. With their restriction of what can be developed with their api, i havn't seen it as a forward moving action. 3rd party developers can make or break your product. It's always nice to keep them happy and would definitely explode your business
Shyp is using a combination of technology, logistics, and outstanding customer service to make it easy for people and businesses to send things to each other.
We're hiring several important engineering roles: API engineers, DevOps and QA. Of note, especially looking for talented Devops folks that have had experience with Linux, AWS and Docker.
We've got a lot of exciting problems to solve, and we're still a small team - the opportunity to take on a big role and have huge impact is very real.
Check out our jobs page at https://jobs.lever.co/shyp
Not looking, but based in SF? You might be interested in our lunchtime tech talks - send a note to [email protected] to get on the list.