4 ms·

the problem i have with this approach is it's reinventing the wheel. continuous integration, testing infra, rolling upgrades, deployment, logging, analytics on

the problem i have with this approach is it's reinventing the wheel. continuous integration, testing infra, rolling upgrades, deployment, logging, analytics on that logging, should all get solved problems I get out of the box in 2019

asiachick 7y ago
not surprised on the downvotes. Many devs will choose reinventing the wheel over using existing solutions. Their competitors will be on to release 7.9 while they're still trying to figure out how to ship version 0.2 without losing all the data from 0.1 Batteries included systems are a force multiplier. Engineers like writing code more than shipping. Go to any game jam and watch the teams using Unreal or Unity. Their progress dwarfs those that start from zero. While the teams using the full engines are adding game play features the teams starting from scratch are trying to figure out how to load 3D data or debug why their graphics aren't on the screen yet. It's no different with apps. A good app framework or web app framework gets you to a working state ready to just work on what makes your app different. Starting from scratch means you're still trying to figure out how to get your DB backed up while the other devs are adding features.
- varjag 7y ago
  > Go to any game jam and watch the teams using Unreal or Unity. Their progress dwarfs those that start from zero. Pretty sure I would come out on top with my CoD:MW download then. The point of game jam is having fun while challenging yourself doing what you like. If you can't animate a sprite or draw a wire mesh without game libs then by all means use Unity, Unreal or even Scratch. Nobody's judging. Just don't read too much into it.
- lolinder 7y ago
  OP isn't trying to win a competition, it sounds like they're trying to learn to be a better developer. I know way too many devs (and have been one myself) who can use a batteries-included system until something goes wrong, but because they have no idea how such a system is constructed they can't debug it, or they don't understand why something isn't performing well. It goes with the adage that every developer should implement a linked list exactly once—you should use the standard library from then on, but if you don't understand what's going on under the hood, you'll misuse it eventually.
buboard 7y ago
if your job is about making wheels, you kinda have to reinvent the wheel. Just driving the car teaches you nothing about them

asiachick 7y ago

not surprised on the downvotes. Many devs will choose reinventing the wheel over using existing solutions. Their competitors will be on to release 7.9 while they're still trying to figure out how to ship version 0.2 without losing all the data from 0.1 Batteries included systems are a force multiplier. Engineers like writing code more than shipping. Go to any game jam and watch the teams using Unreal or Unity. Their progress dwarfs those that start from zero. While the teams using the full engines are adding game play features the teams starting from scratch are trying to figure out how to load 3D data or debug why their graphics aren't on the screen yet. It's no different with apps. A good app framework or web app framework gets you to a working state ready to just work on what makes your app different. Starting from scratch means you're still trying to figure out how to get your DB backed up while the other devs are adding features.

varjag 7y ago
> Go to any game jam and watch the teams using Unreal or Unity. Their progress dwarfs those that start from zero. Pretty sure I would come out on top with my CoD:MW download then. The point of game jam is having fun while challenging yourself doing what you like. If you can't animate a sprite or draw a wire mesh without game libs then by all means use Unity, Unreal or even Scratch. Nobody's judging. Just don't read too much into it.
lolinder 7y ago
OP isn't trying to win a competition, it sounds like they're trying to learn to be a better developer. I know way too many devs (and have been one myself) who can use a batteries-included system until something goes wrong, but because they have no idea how such a system is constructed they can't debug it, or they don't understand why something isn't performing well. It goes with the adage that every developer should implement a linked list exactly once—you should use the standard library from then on, but if you don't understand what's going on under the hood, you'll misuse it eventually.

buboard 7y ago

if your job is about making wheels, you kinda have to reinvent the wheel. Just driving the car teaches you nothing about them