3 ms·

Another perspective: Why don't you want your software to be compatible with the system that your sysadmin provides? (Assuming that system is not completely obso

Another perspective: Why don't you want your software to be compatible with the system that your sysadmin provides? (Assuming that system is not completely obsolete). Minimize your dependencies. It's incidentally also what leads to clean code bases.

brianwawok 10y ago
> Minimize your dependencies. It's incidentally also what leads to clean code bases. You also crush velocity. Smart use of libraries lets you ship code 10x faster. Two identical businesses.. one writes all their own code, one is smart about using libraries. Which one makes it to IPO first, and which goes bankrupt?
- noir_lord 10y ago
  That only holds true (as much as it does) if you assume the goal is always an IPO.
- sly010 10y ago
  Are you arguing that you can keep velocity while building up technical debt? The company "smartly" using libraries might stuck maintaining a monster of dependencies that only ever was meant to be an MVP. It will require 10x more engineers and while they might move fast at the beginning, they will only slow down over time. The company minimizing their dependencies and paying attention to their stack will be able to add complexity over time without breaking a sweat. Their costs will be 10th the cost, and they will be able to run profitably. I am not anti-library or anything, but e.g. adding sci-py to your python project just because you need a gaussian function in one place in your code is just lazy. Managing dependencies wisely is one of the hardest thing in software development. It's right after cache invalidation and naming things ;)
- deleted 10y ago
  [deleted]
- prodigal_erik 10y ago
  If the world has already written 90% of the code I need, how likely is it that the remaining 10% is valuable enough to make a viable business?
  - FanaHOVA 10y ago
    Really likely. Code doesn't mean much, it's mostly about how you present it
- nasalgoat 10y ago
  In my experience, the vast number of problems we've had with our mobile apps, especially on Android, has been a developer deciding to use some random SDK to solve a simple problem because he didn't want to take the time to write it himself. Then the app is broken or has memory crashes, or the final binary is 10x the size it needs to be. 9 out of 10 times it's a third party library. This is why I ban the use of them unless absolutely needed.
crdoconnor 10y ago
>Minimize your dependencies. It's incidentally also what leads to clean code bases. Oh hell no. I have wasted far too much of my life maintaining buggy, technical debt ridden reinvented wheels where there was a well maintained package that could just have been used instead.
- deleted 10y ago
  [deleted]
- deleted 10y ago
  [deleted]

brianwawok 10y ago

> Minimize your dependencies. It's incidentally also what leads to clean code bases. You also crush velocity. Smart use of libraries lets you ship code 10x faster. Two identical businesses.. one writes all their own code, one is smart about using libraries. Which one makes it to IPO first, and which goes bankrupt?

noir_lord 10y ago
That only holds true (as much as it does) if you assume the goal is always an IPO.
sly010 10y ago
Are you arguing that you can keep velocity while building up technical debt? The company "smartly" using libraries might stuck maintaining a monster of dependencies that only ever was meant to be an MVP. It will require 10x more engineers and while they might move fast at the beginning, they will only slow down over time. The company minimizing their dependencies and paying attention to their stack will be able to add complexity over time without breaking a sweat. Their costs will be 10th the cost, and they will be able to run profitably. I am not anti-library or anything, but e.g. adding sci-py to your python project just because you need a gaussian function in one place in your code is just lazy. Managing dependencies wisely is one of the hardest thing in software development. It's right after cache invalidation and naming things ;)
deleted 10y ago
[deleted]
prodigal_erik 10y ago
If the world has already written 90% of the code I need, how likely is it that the remaining 10% is valuable enough to make a viable business?
- FanaHOVA 10y ago
  Really likely. Code doesn't mean much, it's mostly about how you present it
nasalgoat 10y ago
In my experience, the vast number of problems we've had with our mobile apps, especially on Android, has been a developer deciding to use some random SDK to solve a simple problem because he didn't want to take the time to write it himself. Then the app is broken or has memory crashes, or the final binary is 10x the size it needs to be. 9 out of 10 times it's a third party library. This is why I ban the use of them unless absolutely needed.

crdoconnor 10y ago

>Minimize your dependencies. It's incidentally also what leads to clean code bases. Oh hell no. I have wasted far too much of my life maintaining buggy, technical debt ridden reinvented wheels where there was a well maintained package that could just have been used instead.

deleted 10y ago
[deleted]
deleted 10y ago
[deleted]