23

15 years ago I had a job interview as technical leader. They asked me about the trendy framework in those days, Struts. I didn't know much to be honest. I actually started to study java the month before. I was 30 y.o. and I managed to sell myself well.

I got the job. I never saw Struts, the real job was to migrate a z/OS application written on PL/I for DB2 (all things where new to me, I programmed something in VB when I was younger, before studying a career in statistics). Anyway, somebody else already scaffolded Struts, I implemented some business logic here and there, and mostly tried to make sense of the monster-legacy.

Fast forward now.
Two months ago I was interviewed on the last version of Angular and AWS devops, kubernetes etc. I managed not to look completely idiot, but honestly, I never went beyond an Hello World in Angular, and kubernetes, well, I like the name.

I got the job as Technical Architect.

First project I'm assigned to: migrate a 15 years old Struts application to cloud.
Somebody has containerized everything.
Somebody will scaffold a dotNet application.

I'll watch. Maybe I'll write some nice powerpoint presentation. Maybe I'll fill in some business logic in some methods.

I wanted really to be a technical Architect and do things other modern people do.

I actually wanted to learn something.

Anyway.
For 160K$ a year is not bad, I wouldn't complain.

Comments
  • 1
    Congrats!
  • 6
    Same shit here... I was recruited based on if I know "best practices" (clean code, automated deployment, etc.) In the real job all this doesn't matter. They just want to have legacy shit done one way or another.
  • 0
    @bzq84 you said it mate
Add Comment