After almost 3 years of professional experience I’d like to specialize more in something but I struggle to because I enjoy almost every aspect of IT: I find front-end really fun, I find very rewarding to build good user experiences and I’m excited for what WASM may bring on the table but I even like to work on the back end on both: legacy monoliths and modern micro services, I love to refactor clunky programs full of “cargo cult” code and redundancies put by people who doesn’t understand the framework they’re using and to make them shine. I’m even good at UNIX/Linux scripting and with Docker (often colleagues asks me advice on these topics) so I’m really tempted to upgrade my knowledge by learning K9S and reading the 1000+ pages of Unix Power Tools to get into operations/DevOps especially considering which the field is the least likely to be overrun by cheap developers coming from a 3 months boot camp.
On top of that I’ve got even into more theoretical topics: I’m following a course on algorithms and data structures in C and in future I want to learn the basics of AI for a personal project but these things aren’t much about employment but personal culture.
Have you got any advice for this disoriented young man?

  • 0
    Serverless is the future
  • 1
    @dan-pud serverless is a gimmick. Functional and event driven architectures are the future.

    Backed by containerization and distributed frontends.
  • 0
    @dan-pud Sure but given how expensive is PaaS at scale most established business I saw in my limited experience prefers to build their own “serverless” infrastructures on physical or IaaS machines using K9S and other OSS technology leaving PaaS/SaaS for few very specific tasks, therefore I believe which containers and K9S skills will be as if not more useful than Azure or AWS skills.
  • 0
    @sariel agreed about frontends, jam stack makes a lot of sense.
    Containerisation is also a good option for a lot of things. However I think serverless will be the default over the next 5 years.
    And event driven architecture is very easy in a serverless context...
  • 2
    Yep that's the current problem with serverless. The migration path is very difficult so established or legacy things will continue because they make money as they are, and that's not a bad thing.
    New things however will (and in my opinion should) use serverless and the advantages it offers
  • 1
    You should believe you got this and get it, and do whatever your heart desires and needs man, you can and will succeed and you can do amazing things with your computer background knowledge and IT is just one of your talents! Keep it up and get to work on your dreams man! Got have your heart in it.
  • 1
    @dan-pud agree with you!
  • 1
    So specialise, but specialise in something that doesn’t stop you enjoying the full end to end development.

    Like specialising in doing all that but in the cloud or something.

    For me, I specialise in domain driven design and modernising legacy enterprise systems.
  • 0
    @TrevorTheRat I was considering to start contributing on projects hosted by Cloud Native Computing Foundation, this way I can enjoy working on back-end programming projects which goes beyond CRUD and in the same time broaden my containers/private cloud skills.
  • 0
    @DEVil666 that sounds good
  • 1
    @dan-pud the term "serverless" is just another "cloud" buzzword.

    In Amazon each lambda is just an EC2 that's stored in a HA memory recall service and can be connected to multiple other AWS services like SQS, S3, or APIGW.

    It's no different than running a container with arguments every time a file exists in a directory, just alot faster since it's been cached in memory.

    "Serverless" is just another way to sell "the cloud".
  • 1
    @sariel serverless is just someone else’s server
Add Comment