Not that it was ever income-generating for me, but I liked LISP. You could write some very elegant (although not readable code) in it :laugh:

It sounds like that supervisor didn't take the time to invest in mentoring of new hires. Which is sad because that doesn't make for a healthy work environment.

Moving from working solo to a team environment requires a change in perspective as well as in process. For example, when working solo, it is easy to rearchitect things and change function signatures but not so much in a team environment especially if there are other moving parts to consider. There is also a tendency to find things wrong with the code or ways that you would have done it differently/more efficiently and then be quick 'to fix things that ain't broken'. Take time getting to know the code and the history behind some of the design decisions (if that applies in your instance) before offering advice on how to improve things. Your advice and experience may well be helpful and lead to good improvements so don't not suggest things at all :-) Since it is a team, you will likely spend a bit more time collaborating and sharing statuses which, at times, will feel like a waste of time (if you're like me and want to get things done). This helps identify potential issues and clear up any false assumptions so focus on those benefits and don't let time wasted be a frustration. You'll just need to factor these in when giving effort estimates for your tasks. It sounds like you're going into this with the right attitude so that's a good start. Good luck and hope you enjoy working on a project that is bigger than just you :)

I have also met one or two good PMs but lately they definitely seem few and far between especially where I work. It is not an easy job and I admire those who do it well.

I agree with you - the precision was a lot better. I also found it therapeutic to clean the mouse - if I was stuck thinking on a problem it was a great way to work on it in the background while cleaning.

:rose: My condolences. It is hard to lose a pet especially when it happened suddenly like that.

There seems to be many advocates for light mode so I would speak up in support of dark mode. :-) I use dark mode and was really happy when Windows 10 offered a dark mode. My screen brightness is set low. I've always used dark mode when its available. In my work place (when we were on-site), the lighting is very low - it seems to be the preference of the majority of the developers here and dark mode works better in those conditions.

How do you know they're never real? You could have won a whole pile of money and not even know ;)

In South Africa we use mileage - like 'What mileage does your car have?' Growing up, it was very confusing to say the least ;-)

My teenagers have got Garmin smartwatches and they seem to work well. I find it helps them keep track of how active they are and keeps them motivated. The ones with music are really cool! Two of my sons have Vivoactive3 and one has just got a Forefunner because his sport is running. If my kids were a little younger I would definitely look at the Garmin Vivoactive with Verizon because it is great to know they can contact you if they need to without them having to have a cellphone to carry around.

Congrats Walt! Your never-give-up attitude is an inspiration to me :-)

1. Mainly ARM 2. VS with custom plug-ins 3. Aviation

I still use Vi every day :)

Good luck! Hope you get it over and done with soon so you can get back to more fun/meaningful things :) Let us know how it goes.

We've had a foam mattress for about a year now and so far, we like it. We call it the marshmallow because it 'hugs you and never lets you go'. I like it because I don't move every time my partner does and it is supportive where it needs to be. It does depend on what position you sleep in though. I don't think it is comfortable for sleeping on your stomach. I find it a little warmer than springs but not uncomfortably so.

We all commit to a single master branch, except for the case of big new features where it would be developed in a feature branch. With 150 developers working on the same code base, it wouldn't be feasible to have each one use their own personal branch and create a bottleneck for those tasked with pushing the changes across to master. Another reason we use a single branch is that it helps with integration testing. If we are all pulling up to tip and developing on the current state of the software, we are much more likely to find bugs sooner.

We have had Visual Studio crash on us. For most, we found that disabling the source control plugin and/or deleting the intellisense file helped. You could try running VS in safe mode to see if the problem still happens (devenv.exe /SafeMode) or you could try looking at suppressed alert messages to see if that gives you any more information (devenv.exe /ResetSkipPkgs).

Thanks. And good luck in your new job :-)

Does this apply to ALL software developers working on DoD contracts or just those in certain roles?

Thanks for the info. It looks quite arduous, especially since you need to meet some requirements to be re-certified every 3 years. It also encompasses a lot of different areas that a person may never be involved with. I feel your pain! I may have to go down that path as well in the future. :sigh: