|
Being a lone wolf it is much easier to work out the average age of my team, and is it greater than yours.
Quote: ....and how they are handling grey beardedness.
Proudly.
When it turned white I grew my beard longer.
"Rock journalism is people who can't write interviewing people who can't talk for people who can't read." Frank Zappa 1980
|
|
|
|
|
i'm a self employed team of one, 60yo this year, been programming for a living for 40+years and feel i'm writing some of the best code of my life, ive learned more new languages and technologies (to me) over the last 2 years including xamarin, python, blazor, net core, & unity to name a few. The only slightly negative i'm finding is that i need to refer back more and more to projects for syntax and snippets as i just can't keep it all in my head anymore, there's just too much of it, but it's no biggie really, but i still look back fondly on the days when the word PC's hadnt been invented, with MS-DOS and character based systems ruling the landscape, when a programmer could actually learn almost everything they needed. I can't remember the words geek or nerd existing then, you were a 'computer wizard' and people assumed you had a brain like a planet as the word 'computer' struck fear into so many heart's - ahhh nostalgia aint what it used to be, but i'm rambling on like some kind of old man...
GL
|
|
|
|
|
I don't have exact ages, but onshore, we have 65, 58, 48 for devs. Our single QA is 35. Offshore, everyone is in their 20's or 30's. Everyone is just as resourceful as everyone else. However, the oldest is the only one that knows COBOL, which we use. Good thing we are retiring the program in the next few years.
FYI: Our offshore personnel are not contractors, but rather just employees in another country.
Bond
Keep all things as simple as possible, but no simpler. -said someone, somewhere
|
|
|
|
|
My one-man team averages 80 years. But that's just because I outlived most of the companies I worked for.
All programming languages suck. It's just that some of them were designed that way.
|
|
|
|
|
4 people report to me and the average age of all 5 of us is 57.
64,63,63,60,37
My boss (36) and I discuss legacy planning all the time as any of the 4 can retire at any time. I'm one of the 63s, plan to retire 12/2025 but have a two week vacation coming up which will make me consider retiring soon.
|
|
|
|
|
Reading the answers I envy all of you! Lone coders (would be my favorite if I could find someone giving me tasks to do remotely) happy teams with people > 40...
I'm 52 and at the moment I'm unemployed. My last stable job was few years ago but I resigned because I had a fight with a manager, then I worked on very interesting projects with startups and side projects on my own but the problem is I have no stable income and sometime they don't pay me at all. So, since 3 months, I'm looking for a stable job or for a good single project to work on.
In 3 months I had many interviews and coding tests, I received a lot of compliments and promises, but... in the end they disappear
I don't know if it's my age, or there are many other candidates, or these alleged employers are just scum. The salary asked was low or average so should not be that the reason.
Let's hope for the future 🤞
Reading your posts brought me good mood anyway. Thanks and best wishes to all
|
|
|
|
|
semi-monthly: Quote: occurring or published twice a month.
bi-monthly: Quote: done, produced, or occurring twice a month or every two months.
Quote: Assuming bi- can be two or twice, bimonthly can be every two months or twice a month, which is a bit confusing and can lead to a big difference in meaning. ... Semimonthly, however, is always twice a month.
|
|
|
|
|
Biweekly has the same problem.
|
|
|
|
|
|
I've half a mind to agree.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
I always understood semi- to mean half (e.g. semimajor), and bi- to mean two (e.g. bicycle)
The use of bi- to mean half may refer to a doubling of the frequency, but is more likely to be due to people using words they don't properly understand.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
I've never come across semi monthly, although semi annual is very commonly used in financial circles.
Cheers,
Vikram.
|
|
|
|
|
Also, biannual which can and most commonly is used to mean twice a year, may also be used to mean every two years, though for the latter it's often sensible to use biennial to avoid confusion.
|
|
|
|
|
Bi-monthly, bi-weekly, bi-annually - I'll never understand why words with such ambiguities are in-use!
When I worked at a banking processing center and they were pushing for "bi-monthly billing" as a feature - half the staff had one definition in mind, and the other had another!
Any attempt to have them adopt less ambiguous speech like "twice-monthly billing" or "two-week-billing" was shown with disdain. Don't be optimistic about explaining why wording is important to any higher-ups in the financial industry. They already had the marketing stuff all printed up and didn't want to be seen as troublemakers.
|
|
|
|
|
Is it just me or is Visual Studio a little lax in understanding when it doesn't need to build, and when it doesn't need to build.
cheers
Chris Maunder
modified 11-May-21 10:02am.
|
|
|
|
|
Not sure what you are saying here - for me, VS builds when I tell it to and at no other time ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Press F5. You haven't changed anything, and you only exited the app a few seconds ago. Visual Studio builds again. Oh, and the "check for build before debug" option? It's turned off.
Mother Microsoft knows best my ass.
Software Zen: delete this;
|
|
|
|
|
Debugging, running Entity framework's Update-Database command, looking at it slightly sideways. It always goes through the whole build cycle.
What happened to the days of simply tracking project dependencies and file changes, and when youhit F5 it says "nothing I care about has changed. We're done"
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: What happened to the days of simply tracking project dependencies and file changes, and when youhit F5 it says "nothing I care about has changed. We're done"
They ended in Visual Studio 2008, which we still use(*) for most of our development. Pilot projects moved to VS2015 and now VS2019 exhibit the problems you cite.
(*) I'm part of a software group working in a company where R&D and engineering managers are all mechanical engineers. Workflow and official documentation, even for software, therefore adheres to hardware methodologies. Changing Tools Is Bad, because then you have to do a complete product regression test, and nobody has time for that.
Software Zen: delete this;
|
|
|
|
|
I have had all kinds of fun with the Batch Build option. I think it is messed up to the point I filed a bug report and was told the issue is behavior by design. I replied that it was a very poor design.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
I've told them that about a lot of their crapware.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Message Closed
modified 15-May-23 19:07pm.
|
|
|
|
|
It must have improved since the last time I used Qt Creator. I had to do complete clean and build's because the dependency checking ignored resource changes.
Software Zen: delete this;
|
|
|
|
|
VS has not a single clue what/when to build or not, if you are not going and explicitly define the project dependencies...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
What annoys me is that if you leave the "properties" page open and close VS, next time you open the solution you get an error because VS is using the project file and can't open it twice ...
This is an annoyance when you release a new version, and then go to the assembly properties to set up the version number of the next debug edits ... which may be some weeks or months off.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
