111–120 of 123 posts
Earlier quoted context omitted.
Those are the prices to build clones of those sites (I think).
yeah, that's what I though at first as well, but Instagram on the Web > Facebook on the Web? =? Tinder > Facebook ??
Send Gigster your app idea and it sends you back that app. So you don't have to talk to developers and they know exactly what you want from your written description of your idea? What could possibly go wrong?
My guess is that they don't actually care. Just looking at the project examples it's clear that they target the "i want a facebook-like app for xk$" elance crowd, good luck with that, bright future ahead (until the not-so-bright people's money runs out).
Earlier quoted context omitted.
> What we need now is a simple program that takes normal human text and outputs a program. Input "write me a program that adds the numbers 1 to 100" and you would get a program that did that. The problem is normal human text is ambiguous and flawed. Case in point: http://www.wolframalpha.com/input/?i=write+me+a+program+that... Correct, but probably not quite what you intended.
Yeah, but when the latency from description input to program output is in seconds, then you could iterate on the description quite fast. It would be like programming, except you don't need to know any algorithms and all the plumbing takes care of itself.
It's a program that I think can be written in an autonomous fashion, but I just wanted to point out that as soon as you start coding non-trivial programs, testing and debugging you're non-specific language is going to be hell. So bad that I think you are going to have to write thousands of sentences, and eventually decide you want a more specific language than English when you can't determine which of the thousands of words or grammatical elements you and the computer disagree on.
“project management is the place where the most human error happens.” Note sure about that. I mean PM's don't write bugs, right?
Earlier quoted context omitted.
It also farms the code around a bunch of non-communicating developers. No, problems on the horizon, keep running towards that iceberg.
Or it could use a really good developer who also can design - on a contract basis. Several iOS developers can do that well enough to ship an MvP. Even more can also spin up a backend with an admin interface on Heroku in no time. Even without any background jobs. I think you guys my underestimate the concept here. I am just mad I didn't come up with it first :-/ The developer doesn't need to manage invoice, other peop…
A company that simply takes a spec sheet and implements it as written will end up with many very unhappy clients.
Earlier quoted context omitted.
What MIT grad want's this job..? My guess is that they exaggerate this quite a bit. The xyz graduates are probably the founders :)
Why wouldn't an MIT grad want to work flexible hours from anywhere in the world?
Earlier quoted context omitted.
Or it could use a really good developer who also can design - on a contract basis. Several iOS developers can do that well enough to ship an MvP. Even more can also spin up a backend with an admin interface on Heroku in no time. Even without any background jobs. I think you guys my underestimate the concept here. I am just mad I didn't come up with it first :-/ The developer doesn't need to manage invoice, other peop…
The problem is that there is often/always a disconnect between what a client says they want, what they think they want and what they actually want/need. What separates a great developer from a merely competent developer is being able to talk to clients and negotiate that disconnect. A company that simply takes a spec sheet and implements it as written will end up with many very unhappy clients.
Then you slowly realize that it takes about as much time and effort to write a comprehensive, detailed specification of the software, as it does to actually write the software itself.
A few thoughts:
1) The talk of an AI to price things marketing fluff. There is no magic AI that can price, for example, the fact that a client changes his mind, or that legacy code has unexpected bugs.
2) The reusable component stuff is not fully deployed yet. I think where it has potential is as app templates. A lot of apps have similar starting points, and it makes sense to encapsulate those starting points in project templates. I am doubtful that this will evolve into a magic solution that makes software engineering easy.
3) The big innovation, from my perspective, is that they are harnessing the spare work capacity of software engineers. It is very easy for a full time employed engineer to hop onto the platform and make some extra cash. I think this separates them from traditional outsourcing shops, or oDesk.
4) Another innovation is that they capture the reputation gains from their work. Traditionally a freelancer would build relationships with their clients, the freelancers reputation improves as he does good work. With gigster, you as a freelancer do not have an external reputation. Gigster gets the benefit of your good (or bad) work.
Largely because of (4) I would be cautious as a freelancer on gigster. The pay is project based, not hourly, which means there is high variance/randomness to the hourly pay.
“He who forgets the past is doomed to repeat it.” https://en.wikipedia.org/wiki/Computer-aided_software_engine... Maybe it IS different this time around. I can see for very simple apps this might be possible. But one of the first questions that often gets asked on projects that I am on is "Is this even possible?"
Technology is filled with plenty of idea that have their second comings: consumer tablets, grocery delivery, etc.