|
|
|
|
|
by r-s
3064 days ago
|
|
"Full Stack" dev here, been coding for 16 or so years. CS degree in there somewhere. I've used every one of those technologies with the exception of Salt (Nothing against it, just have not used it). I don't think I am that much of a rare breed. Some of the AWS technologies many would not be exposed too, but learning an AWS build pipeline is not difficult if you have used competitors. I don't think that is that crazy of a job description. If someone has focused on breadth of skill over depth, you are going to run across most of those technologies (With the exception of some of the AWS services I don't see that much). Ive mostly worked for startups and its not uncommon for me to write front end modern javascript, build backends, orchestrate deployment pipelines and be involved in a sales call all in a single day. I am very far from superman. Its pretty easy to be "Ok" at many technologies. Its pretty hard to be truly great at a single technology. I admire those who truly master a specific technology but I learned that my strength is breadth over depth. I am sure if a truly seasoned JS developer saw some of my frontend code they would have lots of suggestions for improvement, but that is fine by me. I can build stuff which meets the intended goals and generally everyone is happy. |
|
For example, this job post mentions nothing about monitoring solutions like Zabbix or centralized logging solutions like Graylog or message queues like RabbitMQ or any of the myriad specialized data stores, etc.