flamboyantkoala

This seems like it’ll be a really long journey without labeled data. Do you have an idea of how much fraud is in your sample set?

1. Once I felt like I had mastered a language I’d start learning another. The techniques in a new language would teach me things to take back to my primary language. Functional Programming for instance was great at teaching the value of simple functions. Prior to that I’d put everything in Objects which had implicit state leading to sometimes hard to reason about code. Also Objects still have a place for making easy to reason about code.

2. If I saw a new technology I thought would be useful I’d try it on my own before trying to incorporate at work.

3. Downtime at work was used to learn more programming by working on projects that would help make my life easier at work. Bash scripts, improved builds, improved developer tooling

4. In the corporate world. Learn the soft skills, when to talk when to be quiet. How to brag about your work appropriatly to get those raises.

5. Constant learning. Programming changes fast. If I stuck to what I started with my skills would be far out of date and my job selections would be slim.

Asus RoG laptops are so underestimated for productivity. The AMD chips have fantastic battery life and performance.

Recently set up an office on a couple of them, granted it was not this high end of a model but it’s stupid to ignore them for office use.

Also I guarantee she didn’t pick this. This was 100% advised to her by her companies IT group after she repeatedly said her computer was slow. It’ll run all the spyware she downloads with enough cores left over to run excel.

Coming back to code after a year is hard regardless of language. I’ve had C code I came back to after a year that was dead simple language feature wise but hard as hell to follow business wise. I would actually argue more modern features like Union types in typescript has actually made it easier for me. “Oh this function has to handle two cases of objects an object with an id and without an id”

I’ll have to disagree with this. Adding new features is a problem if old things break but otherwise it just makes future programs easier to write.

You should be writing your next set of code with the newest features if they cut down dev time, cut down bugs or make that area more maintainable

I should start by saying I was a middle manager in a large corporation. This may be a different experience in smaller settings.

I think the transition to manager didn’t live up to expectations for me. I knew I would be committing less code and helping clear roadblocks. What I didn’t expect was the bureaucratic catastrophe that is HR and upper management. Often I wasn’t clearing roadblocks as much as insulating my team from terrible knee jerk reactions from above. In example productivity is down let’s bring everyone into the office post Covid. Productivity was not down for my team but going back was the start of it. My top level performers I struggled to hang on to due to HR in acting strict requirements for promotions. Senior needed 7 years and other random rules. That coupled with some not wanting to come in. I remember the most impactful being losing a 4 yr experience programmer who outperformed every senior I had due to those rules.

There were parts I enjoyed. Helping the juniors grow and the surprises I’d get from that. I learned very quickly that a devs initial skill coming in from college or life transitions was not a good way of judging their maximal. I’d have devs come in that I thought no way they’d be a top performer to a few years later being shocked at how good they were and how they flew past their peers. It made the inevitable loss of them more painful. I knew my shooting stars would see better pay and advancement elsewhere.

I really had no problem with the transition from contributing to relying on others. I missed contributing and was good at it but I knew it wasn’t my role. I knew from past experience a manager didn’t know enough about the day to day code to give fine grained suggestions on how to write code.

I was a fast track developer. Was senior in 4 years but involved a few job hops. Many companies require x years to get to senior but for some reason that goes out the window for new hires with talent.

It wasn’t until managing people that it became obvious why I fast tracked and others don’t. There is a huge difference in our industry. I like to use the analogy of sports. You have multiple levels recreational, college, and professional. As you get better you move up but there’s a gate to moving up that some never achieve maybe genetics maybe effort. The difference is it’s all mixed up in programming there’s no divisions you can have a 15 year programmer stuck at rec level and he’s programming with a 3 year college level athlete that’s running absolute circles around him. The productivity gap is huge. If you manage to get a pro level programmer on your team he’ll make the other 3 rec level programmers look like a waste of money. It’s like the elite runners who complete a marathon in around 2 and a half hours and it’ll be another 4 to 6 hours before the slowest finish. That same gap is in the programming world it’s just not as obvious.

So all that said my advice is to find what your skill is. If you seem to be outperforming your elder peers you’ll benefit from aggressively asking for raises and promotions as well as making a job hop every few years if HR stagnates your pay for the dreaded “years of experience” excuse.

You might also eventually get promoted to a point where you find yourself not excelling. This was my experience in management. I became a manager too young or maybe I’m not built for it. After a few years hating management I went back to programming as a consultant because I realized I was on that upper side of the skill differential, I enjoyed coding and now armed with that knowledge of where I am I can ask for even higher amounts of pay exceeding management pay.

You don’t triple your software output by going to the office. You can improve it by getting developers uninterrupted time with a healthy line of workable items ahead of them.

This is probably going to have the opposite effect they desire.

You will be fine without it if it’s indoors.

If you wanted to strengthen the wood and protect it from getting dinged as easily a couple coats of boiled linseed oil will help. Me personally though I’d just leave it alone, I doubt it’ll get enough abuse to warrant the extra time.

Oh totally seen it work myself but I don’t know that it was agile that worked as much as they had a kickass team.

Some teams just jive well. They communicate, they know what each other is doing, and they can plan with minimal waste. And when it’s successful that’s across all roles not just the devs.

In my opinion those teams would have succeeded in waterfall, kanban or their own home brewed strategy as well.

Oh totally seen it work myself but I don’t know that it was agile that worked as much as they had a kickass team.

Some teams just jive well. They communicate, they know what each other is doing, and they can plan with minimal waste. And when it’s successful that’s across all roles not just the devs.

In my opinion those teams would have succeeded in waterfall, kanban or their own home brewed strategy as well.

Interesting you prioritized pointing out on time delivery as opposed to maximum value.

Hits a sore spot, I’ve delivered a lot of useless stuff on time with agile teams. We could have been useless even faster without the meetings.