The whole point I started programming at 16 was to get a job were actual programming would be the main thing.
Tell me your experience and what kinds of programs you work in or industry if you find relevant.
1 meeting a week, for 1 hour.
I work 3AM to 11AM, then about 12:30PM to 6PM on my side gig https://atomictessellator.com
What software stack you're using at hedge fund?
Can you tell how many lines of code did you commit in a first week of December? :-)
Not asking, but asking - what is your hourly rate? :-)
Congrats on side gig - interesting idea!
Yes
> What software stack you're using at hedge fund?
Cant discuss
> Can you tell how many lines of code did you commit in a first week of December? :-)
43 commits, 3440 lines added, 374 removed
> Not asking, but asking - what is your hourly rate? :-)
Wont discuss with strangers
> Congrats on side gig - interesting idea!
Thanks! It's heaps of fun and it's only just started making new discoveries, time to lab-test some soon
Do you use any software methodologies?
Software methodologies for the zany schemes? Not really, I prefer to do exploratory code inside the debugger (I wrote my own which has a bunch of extra extensions) and the others use Jupyter to riff freely, there’s no constraints when exploring
More engineering rigour goes into prod stuff
After doing this a while, I realized that writing the code isn't the part that takes a long time. It's rewriting it over and over because you didn't fundamentally solve what the business was asking for the first time. I prefer to focus on that part of the puzzle now. Making sure it gets done right the ~first time. Help others on the team avoid lava pits that they can't see yet.
I try really hard to avoid writing any code until I am nearly certain how something should be implemented. Exploratory rabbit chases are quite rare for me these days. A younger me would be appalled, but I enjoy a new kind of game - Making the customer happy for minimal effort and then getting paid.
I want to shift from ops to systems programming and find a completely new role.
I’m really good at the debugging and diving into new codebases, but companies don’t like the fact that I don’t really have a previous full time coding role.
Happy to ear how things are going for you and how you have grown technically.
I’m building up Rust skills (1 year in now) to make the jump once that’s more popular. It’s a slightly risky bet (Rust jobs are currently 95% crypto).
I come from a history of being an individual contributor (15 years of that) and I would say overall as I've gotten more senior in my positions I've done less coding as a % of my time, but the coding that I have been doing is individually more impactful or sensitive.
The non-coding part of my time has gone more into mentoring, reviewing, design, business discussions & goal setting, policy writing and implementation, team organization & management, and interactions with operations.
I think that about covers it, but feel free to follow up if you have anymore questions.
I want to be in the 70-90% of coding now because as I improve and move up I will not have had a stretch of deep programming experience.
If you can think of anything, what would you advise me to do?
I think I would need a bit more information about your current seniority and skill levels before I could give you more specific direction. There is always the default answer if you want to move up higher that communication skills are important, and that's true but what I don't see as often is developing the skill to let decisions go and to not only find ways to live with them but actually accept those decisions and move forward with them.
Absolutely speak up if you disagree, and communicate clearly the prior experiences that is helping guide your decision. Talk about your assumptions and where you think future pitfalls might be. If your team or manager decides to go down a road you don't agree with or don't think is optimal... Let it go. Work with it. Try and accept that as a path forward and embrace it. You might not have the full picture, it might be a legitimately better strategy, or you might be right. In any of those scenarios though fighting against the current, trying to go rogue to prove your path is correct. Those will only lead to ill-will. If it does turn out to be the wrong path, don't play the "I told you so card", take the high road and just move forward.
A lot of engineers, myself included, look back at prior decisions more than looking forward. Reflection is important, and lessons can be learned but we're there to build things, not be right all the time. The bigger your team the bigger and more intense things you can build, but only if you're all working with the current of development.
The more you work with your team, the more they trust you and as you gain in seniority you will have a peak of silent "I told you so moments", that's usually when I've found it was time for me to go up to the next level of seniority as its probably time to start mentoring the people around you.
None of this is about getting more coding time, but I don't think I've ever really optimized for that. Maybe think about what you're trying to get out of that coding time. Maybe what you're actually looking for is unbroken focus time, that I have optimized for but also involves working with your team. Communicate with your team that you would like more focus time, propose things like protected afternoons (meetings only in the morning) or meeting free days (I've found Tues/Thurs usually work best for this).
If you provide me with a bit more detail I might be able to give less general advice.
I used to work for Red Hat (OCP on oVirt/RHV, Arcalot/Arcaflow, etc), in a little over 2 years I wrote somewhere around 40.000 lines of code that I can account for with 80%+ time spent, but that diminished greatly around the end as a lot of changes into the "Scrum to rule everything" direction happened, which decreased the amount of code produced by a lot.
Depending on what you do you may want to go window shopping for jobs where coding skills are valued and that are low on process. If the interview process already puts heavy emphasis on your code, that may be a place for you. If, on the other hand, the quality of your code isn't appreciated as long as it works... Smaller companies/projects tend to work better.
I’m in the market looking for something in the intersection of infra/systems programming.
It has been tough to get interviews due to my location and experience, but I know I will manage to do it.
I can only speak from my experience, but what helped me land interviews ( as a gradually built up over the last 3-4 years) was:
- Having contributions in high profile open source projects name-dropped at the beginning of my CV. (Front-load the interesting stuff. Also, these should be substantial works in case somebody goes to check.)
- Having relatively well-known open source projects I built from scratch (ContainerSSH, gotestfmt, etc) in my CV with well-known users I can also name drop. These projects had nothing to do with my day job and I built them in my free time.
- Having spoken at several conferences. This is the most unfair of all since not everyone can travel and having the conference in there doesn't say anything about the quality of the talk, but it seemed to help get through the recruiter filter.
What helped me get through the interviews (again, from my experience):
- Having experience in diving into unknown codebases and problems. Most companies that are serious about coding will have you do live coding, take home exercises, or read some code in the interview. If you do enough work on open source stuff, you'll develop this automatically as you will be jumping into code that's not yours.
- Being able to do TDD in the live coding interview and still finish on time. Nobody I talked to actually does hard core TDD in the industry and most people are stuck with a ton of legacy code, but this is a magic trick that will get you some eyebrows raised assuming you don't mess up the rest of the interview. Also, forget algorithmic problem solving. While at least knowing algorithms and datastructures helps, most companies don't have deep algorithmic problems in their day to day operations, so encountering these in the interview I found to be a minor red flag.
- Knowing the language basics. If it's Javascript, know your type issues or how the runtime works. If you do Go, know parallelization problems and how to solve them.
- Structure your code! On the interviewing side I had to fail too many candidates for submitting code with an unclear/messy structure for take home exercises.
Big no-nos (when I was the interviewer):
- Do not claim you contributed to a project if all you did was a typo fix.
- If you have a Github profile, make sure it's not full of forked repos you didn't contribute to. I will only look at what you linked in your CV, but others will google your name (no matter if it's illegal or not).
- Clean up or set your social media to private if you don't want interviewers to see that. Google yourself, make sure there are no red flags there.
- Don't use ChatGPT/Copilot without heavy refactoring. This is incredibly easy to pick out and not cleaning it up, not making the code style consistent screams that you have no idea what you are doing. Remember, interviewers only have your code to go by as a signal source.
- If there is a woman in the interview panel, make sure you don't just address the guys. We did interviews with my wife and we noticed this a lot. This may just be a force of habit, but for companies paying attention to diversity, this is an immediate red flag. The people who got flagged for this usually turned out to have a culture fit problem in other areas too, but it's worth keeping in mind.
- Leave your ego at the door. They may criticise your code, but don't get defensive! Stay factual, that will help defuse the situation.
- Don't have typos in your CV. Use a spell checker.
Finally, really, don't give up. My experience is just that of one person, I (probably) don't live in the same country, probably don't have the same amount of time available as you do, and I (probably) don't work in the same area as you. My advice may be complete garbage and not applicable to your situation.
Probably 90% of the time writing code currently. Once the hardware product is released publicly it drops to 10% (maintenance) and then ramps up when new significant features are added.
Broadly speaking..
Stage 1: design specs 0% code
Stage 2: prototyping 50% code
Stage 3: the hard work 90% code
Stage 4: selling and maintenance 10%+
It really depends on the position and nature of the responsibilities though. I've had position where at least half my time was meetings, and others where there was just a lot of Slack chatter to work through during the day. Right now I'm on a limited-time contract with a very specific project to iterate on and finish up, so I don't get pulled into peripheral company decision meetings, 1-1s, etc as much. This appears nicely conducive to programming time.
A few colleagues are learning very quickly so looking forward to taking a step back and focus on other things in 2024.
From my experience places where more programing happening are: - mid-big companies where you role could be very specialized - small companies with focus on creating tech products or where tech has lot of impact on end customers (like if fixing few bugs could instantly lead to making additional money for a company)
Companies from non-tech word usually value non-coding stuff much more.
(I currently have about 50/50 rate and sometimes even less)
