3 ms·

This is helpful, thanks! Just purchased the book. I have a pretty solid background in relational db's (SQLServer, MySQL, SQLite), used MongoDB a lot 5 years ag

by jwally 5y ago

This is helpful, thanks! Just purchased the book. I have a pretty solid background in relational db's (SQLServer, MySQL, SQLite), used MongoDB a lot 5 years ago, but kind of let it go. I've built several web-apps via Node.js / Express, and PHP. Most of the front-end work I've done has involved Bootstrap and a templating library (Hogan - a derivative of mustache) Anecdotally, it seems like API integration is big (???) and I've worked with Google's, Twitter's, JIRA's, SAP's, Square's, Stripe's, etc... I get the general use case of Git, and use it; but have to google anything out of "Git add *.whatever" or "git commit -m ..." I've thought about learning React; but didn't know if my time would best be spent there or something like getting a feel for Kubernetes or Jenkins or whatever. Again, this helps. Thanks!

mindcrime 5y ago
Yeah, Kubernetes is another of those things that is really "hot" right now. It's not a bad thing to have at least a basic working knowledge of, in today's IT world. Of course, the issue you have right now is how to prioritize what to do in a fixed amount of time. There are a billion things (more or less) you could do. The challenge is how to pick the ones that maximize your likelihood of finding suitable employment in your desired time-frame after your current gig ends. And it's hard to know for 100% sure how to do that, since different employers value different things. That's why my best advice is kinda generically "focus on things that you know are hot/trendy in kind of a general sense." Now if you knew you were targeting a particular company that you wanted to work for, you could make your preparations more focused. But it doesn't sound like that's the case here.