Offerzen article about high earning developers

_kabal_ said:
Meh, all you need is a 6 month bootcamp.... #FullStackz

Joking aside, you mentioned culture. I would say this is probably our number one criteria. Morals, work ethic, will to learn and teach, etc. Don’t really want brilliant *******s working with us.
Click to expand...

I don't know the state of their codebase etc, but the wife seems to enjoy her work, the people etc. Considering how successful they are they must be doing something right.
 
"Senior developers" catching feelings in this thread.
 
biometrics said:
Are you referring to me? I don't call myself any "level". But I have been coding for 30+ years. So call me what you like.
Click to expand...

I'm saying you are being hostile for no good reason. Can we move on to threads where we do agree on things?
 
Hamster said:
I senior developer should be able to me what the difference between value and reference types are, talk to me about thread safety etc.

If you tell me you are a senior C# developer and you cannot tell me whether the static constructor or instance constructor executes first or what a sealed class is, or
if you are senior Java developer and you don't know the super class' constructor will be called implicitly by the subclass,
or
inner join vs left join, pros and cons of an index on a database table

In fact, just last week I had a guy with 10+ years experience tell me he can't give me textbook answers when I asked him the difference between value and reference types. I didn't even bother asking him if he knew what a stackoverflow exception is.

Point is, if you consider yourself a senior developer and you cannot answer questions like the above or at least try and get close then what type of senior developer are you really? A Visual Studio Developer? All those questions are relevant in your daily coding life. There's nothing "text book" about them.

No offence to anybody here but the struggle to find people worth the money they ask is real.
Click to expand...

For the record I haven't even come close to working for 10 years but I agree with the C# bit 100% if your a senior C# "engineer" as everyone would write it in their CVs. Its like all the experience javascript developers that keep explaining "async" in javascript as if its a parallel thing. Or should I say they explain async as concurrent but explain concurrent as parallel (hope I make sense). I write javascript at work and find myself preferring something like Go because this "Event loop" thing is easy to trip over when you understand it and the other 5 devs don't. Maybe I'm the one who doesn't understand javascript.

I have to say though that I'm not a senior C# developer but I wouldn't have been able to explain the difference between a inner and left join since I use a ORM all the time. I did know for a very brief period when I read on it and used it in a project once but have since forgotten. Even now I don't feel like looking it up. But the other stuff like indexes are very important even when using a ORM. I can write SQL queries but the queries I used to write didn't use joins most of the time. I'll just google the difference when the need arises but I don't see myself want to be on a team where there is a ton of inline SQL in the code.

But I agree with your statement in general. What sucks is the people that disagree and yet they are lead devs and do code reviews. I wonder what they say when asked about why the did something in their code base. The answer is probably never technical and more like "that's how I've done it for 10 years you dude with less than 10 years experience".
 
very good article ive been debating this for a while now, it resulted of a discussion about php dying. However most stats that we were using were not limited to south africa in which im sure the environment in job procuring is slightly skewed at times.
Some junior devs are earning nearly double the average salary of their experience bracket - and that with little to no work experience. This raises the question whether there are other factors coming into play when companies decide to pay a premium price for a fresh graduate or junior developer.
Click to expand...
This says it all to me. Most of the time you see old lets say php developers bored and move to something new and fresh, like python , now we have a bunch of millennial who trended on python applying for those same jobs, in most of the world you would go for the more experienced developer given he is not like 35+. Not is South africa it seems. What usually happens is as these older web developers move to python it leaves gaps in the php market and thats where most start up developers go into, which in my opinion isnt a bad thing,, if you have php and java down you can read python like a book, get a few years experience and then move on. Web development is changing from the know on language im a front or back-end guy... Jobs are becoming less about what you know but who... My point being that i would not rely on these statistics to give you an accurate measurement of salary expectations it seems incredibly up and down even in one language, smaller companies, most of them have not even considered python, and stick to php. Because implementing it wouldn't give them any advantage as they are now, different stories for corporations though. Just my 2c. I am now surprised about java and c... they arent in trend now, nut they sure as heck know how to stick around, because they are solid. Give it a few years until this washes over. Those two will rise again.

However a very goo article im also happy its relevant to our location super stuff.
 
schuits said:
To be fair not everyone interviews well.
I've been in the business for 18 or so years, but still won't be able to tell you what polymorphism is. Yet I probably implement it every day. If I wanted to go for interviews I'd have to study my theoretical knowledge and take practice interviews.
Click to expand...

If you can't explain polymorphism after 18 years you have a problem.
 
Does it not bother people that the article sees .NET and C# as two different languages?

As experience increases, so does C# and .Net popularity. This is potentially due to senior developers working at corporate companies utilizing these languages. The scarcity of these two languages amongst the junior high paid outliers could indicate future decline in adoption and popularity.
Click to expand...

Or even worse actually, that .NET is seen as a programming language?

Even looking at the graphs and such.
 
Solitude said:
Does it not bother people that the article sees .NET and C# as two different languages?



Or even worse actually, that .NET is seen as a programming language?

Even looking at the graphs and such.
Click to expand...

Yup had the same thought when I saw this
 
Hamster said:
ie. banks pay "senior developers" a lot of money and throw a lot of benefits at them so that they just won't leave.

Salary-8_graph5@2x--1-.png
Click to expand...

The difference in finance, payments and investment software paradigms is that context and experience counts. I can hire a senior dev with 8-12yrs experience but he will suffer doing what we do because he won’t have the correct framework experience (easily gained pending personality) but also the context language will be a steep learning curve and the combo would frustrate them endlessly because essentially he is a junior again (not programming skill but context) and context matters a lot more as the dev is stupidly easy (and yet we get paid lots haha). That’s besides the other factors we deal with often such as poor specs (pending bank, country), fill in the gaps solutions, radical solutions that no-one does, stress, delivery yesterday, etc

This reminds me of when I use to telecoms dev work(ask a telecoms software eng guy about the volumes of data and slippage time an outage can cause).. because I am a telecoms engineer, knowing what the data came from meant I knew how/what the use case was(from operational to billing). As a result I found work more fun, knew what data I was working on and I dunno.. I just got things done faster.

Anyway if you in the Fintech trifecta of tech, enjoy the context then you never really have a career or finance issue as long as you capable.
 
Pho3nix said:
Honestly after working with juniors at a corporate, it makes better sense to start at a body shop. You'll cry because they want delivery and you'll be better for it, while some at corporates are getting big chunks of have never written decent code.
Majority of devs at the corporates are grad's who never left and can't get the salary they deserve elsewhere, that's why most body shops devs are still running the "important" systems in those companies.
Click to expand...

Yes and no. I disagree.. it’s about risk, staffing (experienced specialist staff takes time) and how the ceo/cto/cio will allocate those funds.

It’s easier complain about a dev shop and pressure them than to do that internally. The way you write off costs and risk also is different as if one vendor doesn’t work.. u get another. Staff u can’t do that with easily especially in SA.

Most successful and hugely profitable large corp(where it is not their primary business function) have staff to handle the minor stuff + Arch +/- Soln Arch (larger scale) +/- PM and get specialist dev houses to do last weeks work, yesterday and delivered today haha.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X