Ask HN: What would you work on if you had 100 devs
I was wondering after the discussion of Googles crazy hiring, If you just had such a number of developers that you then had to find a reason to justify within a year or two, what would you work on? Would your perceived quality of these developers impact what you aimed for, and what would you do to assess their quality?
Maybe the question is a bit broad but if you have a direction you're interested in taking this what-if, please run with it.
14 comments
[ 2.6 ms ] story [ 42.4 ms ] threadnote: this is possibly only viable with a large enough number of devs (>100) and enough money to spare.
I'd talk with all of them and help them build multiple teams, by identifying leaders and we'd try a couple of business models. You don't need that many developers to work only on one thing.
Only down the road, when you have something that resembles more like a product and a proper team that increasing headcount will yield more work done. You need to build and grow the team based on the scope you've got.
It goes without mentioning that you need people from other areas, like sales, to do anything useful.
Humm.. An AI system for teaching reading and math to kids. Something that would learn where the student is weakest and adjust automagically. I might even include teaching kids to code. But as a game like system.
Depending on skills the easiest path to success might be to open a developer consultancy type of shop where they work on other people's projects.
People don't appreciate how secure things can be if you use these correctly.
The source host polls a desired set of things in the network it can access, and puts them all into an internal buffer, and transmits that data, plus a lot of forward error correction, and KEEPS sending it, to the matching destination host.
So, if you have an industrial system, such as an oil refinery, production line, etc., you can have the source host poll for status from the PLC, etc... and then forward that data to the destination host outside the firewalls, etc. Remote users will be able to view the status of things as they get updates, using web or whatever protocols you like, but have ABSOLUTELY ZERO chance injecting data back into the industrial system.
It's simple enough in theory. But widely underused in practice.
-
I guess the answer to OP is “a site”?