3 ms·
Congratulations on a cool project! There seem to be a lot of people here who are wondering why you bothered doing this instead of buying/renting/paying for som
by angersock 15y ago
Congratulations on a cool project!
There seem to be a lot of people here who are wondering why you bothered doing this instead of buying/renting/paying for some other solution. I'd suggest quietly acknowledging their points, and then going back to working on cool things.
Be an engineer. Be a problem-solver. Be a thinker. Don't worry about some magical valuation of your time and how learning to roll-your-own is just cowboy development--that's bullshit the suits will feed you to try and make you reliant on their capital. Do the hard things, and you'll go far.
(oh, and look into em-websockets...some cool stuff there if you don't want to mess with a full Rails deployment)
- peteforde 15y agoYou busted me! I'm a suit: https://vimeo.com/4031833 https://vimeo.com/4031833 I fail to understand how delegation is not problem solving, but I know that it is most certainly smart business. Engineers need to manage their time and their priorities, and building a socket queue is a solved problem if you let it be. Why not spend that energy on UX?
- angersock 15y agoSir, you have fantastic moves. :) About UX: that's an issue for the designers, yeah? I imagine the wheel-reinvention should be left to your engineers. In general, I'd agree with you delegation is a good idea, but if you look at the site for the OP, it's a hackathon site. My assumption is that daraosn is more on the dev side of the dev-biz spectrum. It's really counterproductive and harmful to the dev ecosystem to keep pointing out that whatever we're working on, well, it already exists, and we just have to pay for it and move on. That's just my opinion, mind you, but I hope some share it. At the end of the day, we already have operating systems. And web stacks. And programming languages. Anything you pick, anything at all you use for your business, has probably been done before and probably better. We stand on the shoulders of giants. That said, it's important sometimes to reinvent the wheel. It's important to scratch tech itches, even if your biz guys are breathing down your neck and trying to convince you that you're wasting time and investor money. The big problem I have, as a developer, is that there are a lot of paid services to solve problems. But, sometimes, they don't work, or they have bad APIs, or they get acquired and go away. Moreover, every time I outsource part of my stack, I'm reinforcing to the biz guys "Hey, us devs? Yeah, we're just cogs. Find somebody else to replace my sliver of logic integrating all these off-the-shelf APIs. I'm not really that important." How much progress in tech has been made by people reinventing the wheel?
- daraosn 15y agoGreat comment!
- StavrosK 15y agoThis[1] was the most fun I've had in ages. MongoDB already exists, but this was just a blast to write and is great to use. I agree with both you and peterforde, you guys are really arguing about orthogonal issues. [1] https://github.com/stochastic-technologies/goatfish https://github.com/stochastic-technologies/goatfish