Some years back, I started a company with an excellent product manager, one very focused on actual user impact. One of the first things we did is build a tiny, cheap usability lab; every Tuesday we'd have 4 users in to try things out. We rigged it so engineers could watch the sessions remotely, and for the sessions we didn't watch, he'd share key bits. It was really satisfying to see stuff getting used, what worked, what didn't.
Later, as we grew, we still kept the user tests, but added on a slick system for experiments. All of us were involved in thinking about what to test next, how we could make things better. My cofounder was definitely the best at that, but we all made contributions. We all were engaged. We all paid attention to what we were doing for users.
And it helped that despite being a startup, we were big on automated testing and pair programming. When my mom got sick, I took two weeks off and everybody was fine without me. They carried on releasing a few times a day, trusting in each other and in the safety net we had built for ourselves.
It seems to me that the average development process, which is generally about building whatever people with organizational power want, is emotionally corrosive. It wears us down, because it isn't satisfying on a human level. Which, IMHO, makes it way less efficient.
It’s been difficult for me to reconcile these feedback loops and whole-team involvement with the current online push for asynchronous workflows. In my experience, the developers who want to isolate themselves at home or in their office, pull tickets out of a queue and submit a PR at their leisure were the least likely to succeed at improving the product. The developers who never hesitated to jump into a discussion or meeting with the rest of the team or get involved with the product planning sessions were the ones who moved the product forward the most.
Don’t get me wrong: There’s a time and place for isolated, heads-down work. Frivolous meetings and endless planning sessions must be minimized in favor of action. However, the current online mentality in favor of asynchronous work, minimal real-time in-person interaction, and strict “not my job” separation of developer/product manager roles is swinging the pendulum too far in the other direction, IMO. Everyone, from developers to customers, tends to be happier when they’re all included and active in the decision making processes.
For what it's worth, I've worked with a couple teams that were remote and great at this, so it's not impossible. One was a small startup. The developers had worked together in person for years and were really well bonded. Once they added in some remote pairing, it was fantastic. The other was a Mozilla team where they put a lot of emphasis on close collaboration. Between the two, I have a fair bit of hope.
Maybe one of the silver linings of this mess will be that people are more familiar with screen sharing software after this.
This was freelancing though; I had full freedom to do things my way, which is how I ended up working for two weeks to learn about their problems.
And I still prefer delivering food to working on the software. Thankfully, they're super happy with it and there's not much left to do.
Two screener tricks that I recall:
One is getting in a little market research. Add a few questions that you've been wanting to know anyhow.
The other is including plausible-sounding answers that let you reject liars. For example, we had a grid section that asked, "How often do you use these sites?" One axis was frequency, "several times a day", "daily", a few times a week", etc. The other axis was the name of a bunch of sites, including popular things like Facebook and Amazon. But we'd also make sure to include more obscure things, and a couple of entirely fake ones.
My wife does live production (AV) for big shows and concerts. It's a stressful job; for a lot of it, you're on tight timelines and have one chance to get it right. Any mistake you make is pretty clearly obvious to all of the people in the room. You plan the shit out of it ahead of time: one missing item on a truck can be a (pardon the pun) show stopper.
But like you said, at the end of the night, when the trucks are all packed up, you get to go home and never worry about that particular job ever again. If something went wrong, there might be a post-mortem the next day with lessons learned for next time, but it's over.
Some days I am thankful that I don't have her job. Some days I am jealous that she gets to walk away from it all at the end of the night.
I could be wrong though. If you end up just genuinely being a restaurant person, maybe occasionally doing some coding to supplement your income, that's fantastic. There are many things I loved about the restaurant industry.
When I left the store at night, every customer had been served, every piece of equipment had been cleaned, the money had been counted. I was just done. It felt great.
I solve problems every day, I never get done, every day its something new that needs fixing. Every year that passes I feel more and more that I'm just not made for this kind of work :(.
But, money and easy to find a job.
At the time, I simply couldn't understand that. Sure, I hadn't been writing code as long as he had, but I couldn't imagine enjoying anything more than that. I absolutely loved twiddling bits and watching mechanical systems do what my code told it to.
Fast forward to now. I still really enjoy software/hardware/mechanisms/coding/design etc., but if I had to give it up tomorrow, I know I could find something I love just as much.
It's a really big world and there are a lot of sandboxes to play in.
LOVE this.
Without any kind of specifications or design meetings beyond a 5 minute chat here and there.
It was your idea? What did they say, they were surprised?
The guy who's running the restaurant together with his wife is/was an engineer, he hasn't done any coding but he knows enough to be aware of the specification problem.
I'm curious about if you get paid / if you charge software developer rates when working in the restaurant?
The only stressful parts were getting there on time after work (because I tend to linger at work doing that one last thing) and the parking tickets because it was so limited and some spots required top-up payments (before apps). I ended up in tennis-wear because a mature person giving frank opinions of how things look on people (mostly women shopping) seems effective. Anyway I lasted longer than most of the younger hires and gave it up part way through the winter because driving/parking in that was just too much. Maybe something like that but outdoors might be a great thing to try.
Every new system an organization takes on requires maintenance, training, etc. This takes time from the coders and is frequently not taken into account.
Developers stay at companies for 1-2 years, so it seems like you get frequent resets.
I've been at the same place going on 8 years. My father in law has been at the same place for 30.
tbh same. I'm great at what I do, but I still very much miss the restaurant environment / more directly helping people.
You're only there for 2 weeks, you know you're only there for 2 weeks and everyone knows you're not going to get the terrible end of the stick unless they're specifically going out of their way.
I delivered a lot of different food in high school and it honestly was one of the worst jobs of my career, I'd much rather work in retail or clean pools. All of my income went into gas and repairing my car. If I got a tip it was a few bucks and back then we had the 30 minute delivery thing that caused so many drivers to get into wrecks I'm pretty sure it was eventually banned or made illegal (or they all just dropped it).
The car is provided by the restaurant, and it's large scale corporate customers so no tips.
I make enough money to survive, a chance to make people happy and get free food. I've been doing this for several months now.
It is a relaxing job when it's going well and not rushed. I like driving around aimlessly.
To my surprise I found that I actually enjoy delivering food more than writing code. As long as the customers get the food they ordered delivered in time, everyone is happy. And once I'm done, I'm done. No more lying awake at night going back and forth over some design decision and worrying about consequences from choices already made.
It's not as mentally stimulating, and I earn way less money, but I'm finding it harder and harder to find the motivation to go back to writing code.