How programming has changed over the last 10 years?

Splunk
KyaBakteHo

Go to company page Splunk

KyaBakteHo
Aug 19, 2021 10 Comments

In terms of.
1. Programming best practices(Functional vs Object Oriented)

2. In terms of library use and availability.

3. Tools packaging runtime such as docker kubernates etc.

4. Overall cloud adoption and cloud native thinking

5. Anything else.

10

comments

Want to comment? LOG IN or SIGN UP
  1. TOP
  2. RECENT
  3. OLD
 TOP 10 Comments
  • Shopify
    fLmB72

    Go to company page Shopify

    fLmB72
    Well programming was an activity of highly skilled passionate hackers who eschewed large companies and processes. Now it's a bunch of coding monkeys doing leet code and dying to work at FAANG.
    Aug 19, 2021 2
    • Google
      owqJ68

      Go to company page Google

      owqJ68
      And getting paid a lot more. But dude, FAANG are all more than 10 years old.
      Aug 19, 2021
    • New
      yGUI73

      New

      yGUI73
      Like if the change from 20 to 10 years ago was any different. You are just getting old.
      Aug 19, 2021
  • New / Eng
    johnjacoba

    New Eng

     johnjacoba
    1. Functional and Event/Data-driven. There is still OO but you dont see it, those eng work in the basement getting πŸ’ΈπŸ’Έ

    2. Overdependency on public libraries

    3. Hyped initially but died down, useful in some large scale but not for the little guys

    4. Cloud still moving steady and is here to stay, the dinosaurs will eventually catch up

    5. Too much bootcampers, not enough people with passion for programming these days
    Aug 19, 2021 0
  • Datadog
    tatertote

    Go to company page Datadog

    tatertote
    GitHub has become the defacto source control system. 10 years ago, the winner wasn't settled

    Java used to be the king. Today there are more competitors

    Today's software development is mostly configs. Too much yaml. Configs are made to generate more Configs. There wasn't this much config kludge 10 years ago.

    Average quality of engineers is higher today. But corporate politics has become 10x higher, largely because non tech people (hr, PMs) are making decisions and dumping them on engineers. If engineers stop doing the work, nothing will happen. Engineers should leverage that to demand respect.

    Kubernetes makes everyone feel like a new era of distributed systems has been invented. No. It's the same thing with VMs on repeat. K8s does bring standardization.

    Slack was not the defacto tool of communication. Email was the cool shit. Distractions were lower because no notifications and everything was a bit slower paced.

    Very little agile, scrum bullshit 10 years ago
    Aug 19, 2021 0
  • Adobe
    VwME74

    Go to company page Adobe

    VwME74
    3 words leet code monkeys
    Aug 19, 2021 0
  • Jacobs
    gl4sn0st

    Go to company page Jacobs

    gl4sn0st
    1. Same as 10 years ago. I.e., There are companies with teams who use good practices and those that don't. This isn't to say that a team with bad practices can't have other pros than team with good ones.

    2. There are more libraries, there is more support, there are more users. This helps users of these libraries to choose them easier. NPM / Maven dependency store and others handle this well by showing you popularity / download frequency, etc. absolutely awesome imo, makes my life easier.

    3. I don't know what containerization looked like 10 years ago, but being able to dev on one machine, and deploy on a completely different OS and machine using something like docker compose and retain all functionality is also very awesome.

    4. Better out of the box security, easier to scale vertically and especially horizontally, easier admin'ing.

    5. Mass remote work adoptation. Yes, this is a new one, but if there are less and less engineers on prem, this means cloud will expand.
    Aug 19, 2021 0