Cover image for New Job New Tools

New Job New Tools

xanderyzwich profile image Corey McCarty Originally published at coreydmccarty.dev on ・2 min read

I recently started a new job, and it's only the second that I've had in my dev career. With a fresh look into how different it can be between companies, I thought that I'd share a few thoughts. I'd also love to hear yours in the comments.

Old Busted

I started off as a full time employee of a vendor company providing onsite/offshore model software development and support for a large logistics company. As such I never had much say in the tools that were being used. The company decided against allowing anyone to have admin rights on their local machine, and their 'official' take on IDE availability was that "Eclipse is the corporate standard and we will not consider making any alternatives available." Which was fun. This was even more fun when the vendors lost their desktop licenses for Microsoft Office when we moved to 365. It was also especially cumbersome to work from home when the vendors could not access the code repository or the test servers via VPN. Instead, you had to connect to vpn, then log in to a virtual server (after many failed attempts), and use whatever software was installed there to do your work. Overall, it seems like there was more concern with being secure than being productive.

New Hottness

I can't adequately communicate the glee that I experienced in my first week of work. I was given the option to have full license of IntelliJ IDEA or Eclipse. I got GitKraken, desktop applications for Office, local admin on my machine, the full Atlassian tool stack [Jira, BitBucket, Confluence, Bamboo] that auto-magically works together, and an account with Pluralsight matched with a standing calendar block to study every week.

While it has been a bit weird transitioning jobs during the pandemic, I have had the greatest experience with getting help with things. Everyone that I've asked for help is willing to stop and assist as needed. The work tasks are well defined, small units of effort with recommendations for solution. All that was necessary was to apply the change as recommended and then test. As I've needed access to an system I've been able to quickly request it and have it granted within 24 hours.


It's amazing how much different life can be in a new position/place. If you are in a tough spot, keep at it. Build your experience as you look for work, and eventually you will find a place that works well for you. Currently I can't imagine a reason that I'd leave my current role.

Cover image by undraw.co

Posted on by:


markdown guide

I'm fortunate enough to have had a personal licence for the Jetbrains toolkit, so when I changed jobs I was able to use that. I went in as a lead dev to make improvements. Now the full team and any new hires get the full jetbrains toolbox. They love it


You're doing the lords work. Thank you!


It's not at all selfless, I got a year's free licensing out of it, whilst my employer got a 20% discount.

I think Jetbrains still won.

You won and so did your coworkers.


That first part in Old Busted is an interesting discussion. What is the balance between productivity and security?


I expect that the security decisions were made for all of the company based on the fact that the number of people that should have local admin is a subset of the people with AD accounts. I agree that most office personnel shouldn't have local admin, but if you trust someone to write code for your production servers and to be able to execute application code on said servers then MAYBE you should trust them to not nuke their primary means of employment/productivity.


Absolutely agree. And the separation of powers at bigger institutions can make things difficult. I think for the general user at the institution admin rights should be restricted. Here, for example, I had to put in a service ticket to gain admin rights, but it is only because they know me. Security vs Productivity is just an interesting dynamic to me. Information services tends to hedge more towards security at the cost of productivity while developers tend to edge towards productivity at the cost of security, from my experience.

I do enjoy the way that Windows has evolved to handle this over the way that it used to be. Just because you have local admin doesn't mean that you run everything from that privilege. Having the prompt before you run something as admin is a real benefit.


Bravo and congrats on the new job. It sound like a world of difference in culture and developer happiness/tools.


It really is a lot different. I had no clue that a moving companies could be so much different.


Man I'm glad you're having a great start. Even happier you're writing again! 🤓 This emoji has been brought to you by {WIN .}