You're right! The company is very openly continuing layoffs for the next 2 years, so I don't have much faith in the team I was moved to sticking around for much longer. I fixed up my resume and started applying elsewhere the week after everyone I work with was laid off. The job search is going well, fortunately.
Location: Westchester, NY
Remote: Flexible
Willing to relocate: Maybe
Technologies: Java, C#, .NET, Javascript, Ruby on Rails
Résumé/CV: http://linkedin.com/in/matt-borkowski
Email: matthew.p.borkowski@gmail.com
I'm a current Masters Student, working towards my M.S. in Computer Science. I also have a B.A. in Music! I have ~2 years experience working as a Software Engineer. Looking for a summer internship - willing to talk about the right fulltime role as well.
About to turn 30, still struggling with what I think you’re talking about.
Have you tried examining what it is that actually gets you to work on those productive days? I wonder if you’re glossing over that part while you focus on what’s getting you into those unproductive days. Are you waiting until you get to sort of a critical mass, until feeling lazy feels bad enough that you can’t handle it anymore, and that’s your motivation for getting back towards being productive? If that’s the case, it might be worth contemplating how sustainable that is for you, and if there’s anything more sustainable you could use for motivation.
You seem to have made up your mind about the advantages of TypeScript. The word "evangelism" has come up several times.
I'm a fairly junior dev, but I'd like to suggest caution to anyone who might be inclined to think that a technology like TypeScript will represent a clear step forward for anyone looking to take a step into 2022 and leave Javascript behind. The "evangelist". "Organizations/decision makers who haven't adopted TypeScript yet just haven't been exposed enough/had enough misconceptions debunked, and they need to get on the same page with faster moving companies, or get left behind".
1) I don't think this is how most successful companies/orgs think. 2) It seems to me that, as is the case with literally almost every choice of technology or solution, it's a matter of tradeoffs. Pros and cons. What are the honest disadvantages of your company adopting TypeScript? What are the opportunity costs, or how much quicker could you have addressed urgent sprints if you had left the JS alone? Be honest. Will there be a learning curve? I have to imagine there would at least be some friction... I don't think writing good TypeScript is as simple as doing a 1 hour tutorial plus some fiddling, or taking out a week. The other thing to weigh against that is, companies literally never have time. There is never enough time to do everything that you want to do, especially when it comes to stuff that's probably seen as more quality of life centric. Business oriented people want and are under pressure to put out features, tangible stuff.
The sooner you come to grips with that kind of stuff, will probably be the sooner you can do a solid job of framing and selling TypeScript. Be honest about the drawbacks, and then you can give them their due, while making sure that in your pitch, the payoffs are impossible to ignore. My final piece of advice might be to be a bit more gentle in your pitch. I've definitely run into some friction with what felt to me at that time like stubborn and short-sighted decision makers. Maybe the best thing you can do is to, again, frame the pros and cons, give them a fair and even-handed lay of the land, facts only, and then let it feel like it's them that's coming to the decision to use TypeScript. Almost like Jedi mind tricks.
Hi! I'm Matt, and I'm a full stack developer. I currently work in an enterprise environment on a .NET/Vue.js stack (it's my first dev job), but I don't necessarily like to confine myself to just those two technologies. I work with a small team, so everyone often ends up doing a little bit of everything. I work on things from implementing new features and fixing bugs, to working on developing a testing suite in Selenium, to working up mockups in Figma and presenting them to the business end, to making some recommendations about ways to move forward architecturally.
Prior to this, I did a bootcamp. Prior to that, I worked in insurance, developing some tools in C# to help automate my daily tasks. And prior to that, I got a bachelor's degree in music.
