4 ms·

It took me forever to understand what each services aim to do. Like I could have literally been a better programmer by spending all the time learning algorithms

It took me forever to understand what each services aim to do. Like I could have literally been a better programmer by spending all the time learning algorithms instead of figuring out what each of the aws services do. I wish I've had access to this post before. I like the services they offer, I just really hate the names they gave it. Funny enough, Jeff Bezos said in an interview that names of a product is important #irony

mattmanser 11y ago
You've got a nasty shock coming then, you'll spend far more time scouring badly written documentation about something that is supposedly simple but just doesn't work and once you've got working you'll never, ever use again until you've forgotten everything and then you need to set it up again and you'll have to go through the whole soul destroying process again but the documentation you find is now out of date, why-god-why, than you ever will implementing algorithms. In fact, if you spend more than a couple of weeks implementing algorithms in your entire career you're probably doing it wrong or part of the 0.1% of programmers working on low level libraries.
- jimbokun 11y ago
  Now re-read your first paragraph in light of the second one. Sometimes, it really is easier to just implement something your self than go through the "soul destroying process" of figuring out how to correctly set up and configure a library, framework, or piece of open source infrastructure. Not an algorithm, but it can be a lot easier to write your own SQL, for example, than setting up and configuring Spring and Hibernate. (Talk about soul destroying. Yes, I am a Java developer, why do you ask?)
  - Anderkent 11y ago
    > Sometimes, it really is easier to just implement something your self than go through the "soul destroying process" of figuring out how to correctly set up and configure a library, framework, or piece of open source infrastructure But then the next person to look at your code has completely 0 support, rather than the very little support they'd have from the crappy documentation and stack overflow if you used an open source library.
    - mattmanser 11y ago
      Yes, if you do what jimbokun suggests you're definitely doing it wrong. Edge cases will consume months of development instead of spending a day or two wrestling with poorly written error messages or badly documented APIs. The one I always hit in .Net development is logging, log4net and elmah are both abysmally poor at documentation, but incredibly easy once they're actually set up.
  - kevindeasis 11y ago
    I remember making project using spring. I still have night sweats thinking about it. I'm really happy with node and scala play framework
- deleted 11y ago
  [deleted]
- joesmo 11y ago
  Your first paragraph is a perfect description of working with AWS.

mattmanser 11y ago

You've got a nasty shock coming then, you'll spend far more time scouring badly written documentation about something that is supposedly simple but just doesn't work and once you've got working you'll never, ever use again until you've forgotten everything and then you need to set it up again and you'll have to go through the whole soul destroying process again but the documentation you find is now out of date, why-god-why, than you ever will implementing algorithms. In fact, if you spend more than a couple of weeks implementing algorithms in your entire career you're probably doing it wrong or part of the 0.1% of programmers working on low level libraries.

jimbokun 11y ago
Now re-read your first paragraph in light of the second one. Sometimes, it really is easier to just implement something your self than go through the "soul destroying process" of figuring out how to correctly set up and configure a library, framework, or piece of open source infrastructure. Not an algorithm, but it can be a lot easier to write your own SQL, for example, than setting up and configuring Spring and Hibernate. (Talk about soul destroying. Yes, I am a Java developer, why do you ask?)
- Anderkent 11y ago
  > Sometimes, it really is easier to just implement something your self than go through the "soul destroying process" of figuring out how to correctly set up and configure a library, framework, or piece of open source infrastructure But then the next person to look at your code has completely 0 support, rather than the very little support they'd have from the crappy documentation and stack overflow if you used an open source library.
  - mattmanser 11y ago
    Yes, if you do what jimbokun suggests you're definitely doing it wrong. Edge cases will consume months of development instead of spending a day or two wrestling with poorly written error messages or badly documented APIs. The one I always hit in .Net development is logging, log4net and elmah are both abysmally poor at documentation, but incredibly easy once they're actually set up.
- kevindeasis 11y ago
  I remember making project using spring. I still have night sweats thinking about it. I'm really happy with node and scala play framework
deleted 11y ago
[deleted]
joesmo 11y ago
Your first paragraph is a perfect description of working with AWS.