Posts tagged "software developer"

Three Ways To Advance Your Career As An International Software Developer

April 17, 2019 Posted by Programming, Recruiting, Startups, Technology 0 thoughts on “Three Ways To Advance Your Career As An International Software Developer”

Here are the 3 best practices we teach to young developers in our network as they begin their journeys as international software engineers.

1. Think About Time

Do you work with a lot of 45-year-old software developers at your current company? According to a 2015 survey on Stack Overflow (via InfoWorld), the average software developer is 28.9 years old. (Data USA puts the average at 39.7.)

While there are many reasons for this, the bottom line for many developers is that the window to fully develop your professional network may be limited compared to other industries such as the legal profession, where the average age for U.S. judicial workers (including lawyers) is 46.3. 

Sure, it’s tempting to take your excellent pay to go on every available holiday and let your friends know you’re living the good life on Instagram, but it also pays to take some risks early in your career. So take risks.

Risk joining a startup, risk starting your own project or company, or risk asking someone you’d like to emulate to mentor you. As the old adage goes, “Fortune favors the brave.”

While press headlines may focus on the Zuckerbergs of the world, I know plenty of developers who were early employees at technology companies you’ve never heard of that were acquired, and who have leveraged such experiences to leapfrog their careers.

So surround yourself with people who embrace risk. You can easily spot these people and organizations because they’re the ones who are constantly investing in new experiments.

Believe me, not many developers want to join the ranks of those who thought joining my first startup was “too risky.” That company is now worth over $3 billion on the NASDAQ stock market.

I believe the greatest risk for young developers is not taking any.

2. Use IT Outsourcing As A Stepping Stone, Not A Career Destination

In emerging economies, working for an IT outsourcer can be a great place to learn basic skills and get exposure to live commercial projects, but you may not want to think of this as a long-term career prospect. That’s because IT outsourcer culture can be one of employment arbitrage and not innovation, and learning to think like an innovator can widen your career opportunities greatly.

A 2016 Deloitte survey (via The Wall Street Journal) indicated that only 21% of enterprise outsourcing contracts had any “proactive innovation” built into their service contracts, although Deloitte found that number had risen to 43% in 2018 (download required). 

Obviously many innovations come from startups, so working on a startup project could be great exposure to innovation culture and give you the opportunity to put your own unique ideas into production code.

As well, I’ve found that IT outsourcers (especially large ones) tend to work on legacy projects and in legacy languages like J2EE. This can severely limit the types of jobs you can get in the future and rob you of the experience to learn new technologies or frameworks.

A common mistake I see young developers make is thinking it’s OK to work in the “safety” of a large outsourcing company because they and a friend are working weekends on their brilliant app idea. It rarely works.

A 2012 study by Harvard Senior Lecturer Shikar Ghosh (via Silicon Valley Business Journal) found that 75% of venture-backed startups fail, although other estimates vary. Think about that for a second — if founders who are dedicating their lives to their projects with VC money fail three out of four times, what are the chances that your unfunded side project will be successful?

For those that aren’t born innovators, developers can nurture an innovation mentality by working for a company whose culture rewards “outside the box” ideas and fosters risk-taking. That can be a fast-moving corporation, a VC-funded startup, or a bootstrapped group of hungry founders.

3. Find A Great Mentor

If you don’t have a senior coder that can take you under their wing and mentor you, please go ahead and work for someone that can. This is by far the single biggest difference I see between developers who simply survive from paycheck to paycheck and those that continue to increase their opportunities until they decide to retire.

Another common mistake I see young developers make is that they think $500 per month more in the short term is more valuable than working for a good mentor in the long run. In my opinion, they are wrong — good mentors are as valuable as a top university education. 

Look for mentors who are living the life you want and who espouse the values you hold dear. Just because someone made millions and drives a Ferrari doesn’t mean they’re a good mentor for you. And a good mentor doesn’t have to be someone that makes you feel good about yourself.

Think about your best professor or teacher from your school years. Was the person you learned the most from the nicest teacher? Did they challenge you and at times make you feel uncomfortable, or did they sing your praises on a regular basis?

Mentors come in all shapes, sizes and temperaments. You want to choose those that can most accelerate your career and help you train for your “career black belt.”

As Marc Andreessen once said (paywall), “Software is eating the world.” Just make sure you get your slice of the pie while your career still has teeth. Source

Please follow and like us:

How Long Does It Take To Learn A Code Base After Getting A Software Developer Job?

March 1, 2019 Posted by Programming 0 thoughts on “How Long Does It Take To Learn A Code Base After Getting A Software Developer Job?”

There are a lot of articles that talk about everything leading up to receiving your  offer for a software development role. But, after negotiating the offer, and accepting the job, what comes next? Whether you’re a first time developer or a veteran, there’s always an on-boarding process that involves getting up to speed with the specific tech stack that the company uses.

This exact problem is what these companies seek to resolve by hiring the most experienced developer they can find. Still, it requires time for a new developer to become accustomed to a code base. How much time that takes depends on various factors like the developer’s experience with the language that the company uses or the complexity of the code base itself.

Any developer would require mentors or outside help(books, Google, etc.) to succeed. This is especially important to know if you’ve just landed your first development job and the feeling of imposter syndrome closes in. During your life as a developer, you will always be learning some sort of technology that will increase the efficiency of the code. If you’re still not sure, below are some experiences developers have had during the first few months at their new job.


William Britton

Ah man, I remember I started this job as a .Net/C# Developer after being a Java Developer for close to 5 years. I specifically told them in the interview that I only had basic knowledge of .Net but I was willing to learn. Little that I knew, I was the only .Net resource on site to support this project (they purchased a product from a company located in another state with no support).

It felt like the lowest point in my career because it took me so long to get up to speed on how to contribute efficiently. I had to quickly learn Visual Studio/C#, SSRS, SSIS, TSQL, IIS practically all at once. The hardest thing that took long for me to grasp was lamba expressions, since Java didnt have this at the time.

But after a year of working there, I was finally comfortable and making consistent contributions, I learned a hell of a lot and it has helped me succeed in my role today.


Nick Shoup


My first role, I will say took about 3 months before I felt like I was contributing. I’d have some small wins, but then I’d feel like I wasn’t able to contribute when it mattered most. Granted I was a junior developer, and was not used to working in an environment with other developers.

To be honest, I still feel like it takes me about the same amount of time to get fully spun up on a new role, but this also entails more responsibility outside of just developing software, such as working with product owners/stakeholders to understand the road map forward. It seems like the more experience I get the more responsibility I take on. I’m curious to see what others say.


Glenn Stovall

I’ve had different experiences, ranging from a couple of weeks to a couple of months. Here’s what I’ve noticed makes a big difference:

#1 by far is having an onboarding process. Companies that had a strategy and a method for onboarding employees get people working productively 2-3x times faster.

The other factor I’ve seen is amount and complexity of domain knowledge. I don’t need that much documentation on your code base, I need it on the domain knowledge. I can wrap my head around React components and Ruby POROs, what I struggle with is the jargon and intricacies of your particular industry. Who knew that college housing departments could be so complicated?

Another factor that I’ve noticed has an effect is my personal familiarity with the tech stack. The more experience I have with the tools and frameworks, the quicker I can hit the ground running. This one is also the easiest to overcome in my experience. The company may have undocumented internal knowledge I can only learn via talking to coworkers, but React tutorials are a dime a dozen.

Lastly, I would say is the complexity of the application. Even in a complex application, you can usually focus on one small part, or find parts that are siloed away and easier to grasp.

The big takeaway I have after thinking about it is that the codebase is the least important factor when it comes to getting acclimated in a new environment. The process of how internal domain knowledge is transferred is much more important.


Michael Diaz

That depends on the size and complexity of the code base. I’ve been places where 3-6 months was all it took and I’ve been places where 1 year wasn’t enough. One suggestion I have is to learn the product as a user. It gives you the ability to see where the problems are.




I’ve been at places where I was able to start contributing right away, while others I contributed after a few months and other places where I didn’t feel like I made hardcore contributions until about 9 months in. Like you said Michael, getting familiar with the product is an essential piece in understanding the code base.


Gerade Geldenhuys

2 months in at my new place, I’d say I’m now only starting to feel comfortable navigating the project on my own, It is quite large and complex. I bolded starting because I still have a long way to go.


Maxime Julian

I’m currently working as a contractor for a massive corporation. Although as a contractor you’re expected to be fully up and running within days, it still took me a good 3 weeks to get confortable with the project I was assigned on.

Since the codebase was quite old, too many decisions were undocumented or even forgotten; the people who took them having left the company or not remembering why they took them anymore.

Even now, after about 4 months, I still can’t feel fully confortable with our project because there’s too many forgotten decisions.



Micah Vanella

In my first job as a Junior Dev it took me almost a year because we had 3 different very large products and they had an extremely niche user base so I had to become familiar with those processes. As others have said if you can understand the user experience it makes it a lot simpler to understand the code. Since becoming a consultant I’ve had a wide range of experiences. Some times it takes as little as a few days to understand the code, sometimes you never do because the guy who wrote it is gone and there’s no documentation and the users can’t explain how they use it.


Cameron Lepper


I reckon there was no point at where I suddenly felt productive, more so that there was a point where I was absolutely aware, retrospectively, that I actually was contributing.

I reckon, if I had to put a timescale to that, I was probably contributing after a couple weeks, but only contributing with great benefit after 3-4 months or so?

Interestingly, this is only based off my experience with my first software role. I’m about to start my second, so it’ll be interesting to see how quickly I feel I get settled in and contributing.


Rachel Soderberg


It was a few months.. not sure exactly how long but definitely more than one. I’m at 5 months with my company now and I’m finally starting to feel like I have a firm grasp across my domain. There’s still things that come my way where I’m thrown off, but that’s happening more infrequently (which is a relief!).






From the responses above, you can clearly see that it takes about three months for a developer to feel comfortable in their environment. That means being able to contribute meaningful code that can stand the test of a code review in a project. Some junior devs even reported taking up to a year to get a handle of the code their working with. The thing to takeaway from this is that code isn’t something that can be consumed in a day. Since we do not communicate in code, it takes time for our brains to adjust to any code base. What we can recognize are patterns and architecture. Sometimes stepping away and getting a sense of the architecture of the project will reassure inform you about what you need to prioritize learning to maximize your learning curve.


All answers were sourced from


Please follow and like us:

Earn up to $121k per year as a C# developer

October 2, 2018 Posted by News 0 thoughts on “Earn up to $121k per year as a C# developer”

Are you ready to start your C# coding odyssey and earn big bucks as a software developer? You’ve picked the right day for it.

C# is a programming language often overlooked by first-time coders. There are some great reasons to give it a try, and not just because of the huge price drop on the Complete C# Coding Bootcamp right now.

C# (pronounced ‘C sharp’) is similar to C, but it’s generally considered to be easier to learn. That’s one reason why Microsoft developed it. Take C, update it to make it more powerful, simplify the code, and you’ve got C#.

C# developers earn $55k to $121k per year. (Source:

One of the main reasons to learn C# is the number of toolsets and frameworks that support the language, all of which are backed by Microsoft. For example, most developers agree that Visual Studio is one of the most feature rich and powerful development environments on the market.

C# gives you prospects too. It has mainstream adoption on the Microsoft and Unity platforms. Big software developers such as Blizzard Entertainment and Electronic Arts use it. Developers love the language for being easy to use and well-designed. Finally, reports that, on average, C# developers earn $55k to $121k per year.

The Complete C# Coding Bootcamp is the ideal place to start learning. This mega bundle of 11 learning kits — produced by top experts in the industry — is over 89 hours of interactive tutorials and projects to get you C# coding in your sleep.

This online bootcamp also adds a host of transferable skills to add to your resume, such as HTML and CSS which are used in web development. You’ll come to terms with Microsoft Visual Studio, Eclipse, Unreal Engine, Unity, and various other programming environments.

The C# Bootcamp in full:

The 11 learning kits retail separately for a combined $765, but right now you can purchase the lot for just $41. You get lifetime access too, so it’s still worth picking up during the promotion even if you won’t have the time to start for a while.

Please follow and like us: