wrong tool

You are finite. Zathras is finite. This is wrong tool.

  • Email
  • LinkedIn
  • RSS
  • Twitter

Powered by Genesis

How corporate culture excludes me, or why I never bothered interviewing at Amazon, Facebook, and Google.

April 13, 2023 by kostadis roussos Leave a Comment

Every so often, I read an article breathlessly talking about the greatness of any particular meeting process and how everyone should aspire to such a meeting culture. And it got me thinking about my career choices.

I never interviewed at Google earlier in my career because they wanted my grades. My grades undersold my abilities because of my neurodiversity. And anyone who thought they measured me accurately was probably a place I never wanted to work at. And then there was this whole class of companies founded by ex-googlers that I associate with that culture and choose not to even consider. I didn’t trust them to judge me based on deeply flawed metrics.

I never interviewed at Facebook because I saw how they had these all-night hack-a-thons, and I was about to be a dad, and I never wanted to work at a company where spending the night hacking was a requirement for my job. In particular, I knew that the people who could spend time would build social relationships that endured, and I would be formally excluded from them or have to choose not to see my kid. There were these youtube videos of the corporate culture and the hacking, and I was like – Nope, not for me. At Zynga, we introduced hack-a-thons, and folks wanted to mimic the all-night nature, and I remember throwing a temper tantrum in an exec meeting, and we agreed that they would not be all-night extravaganzas.

And so similarly, if a recruiter said ex-Facebook, I was like – probably not the kind of place where wanting to be with your family and in your bed will be a place for career growth.

I never interviewed at Amazon and had panic attacks when folks at VMware wanted to introduce Amazon-style meetings because, again, because of my neurodiversity, I knew it would exclude me. But I was always curious whether it was as bad as I thought.

Amazon came to VMware to have a meeting complete with a six-pager, and I was in the meeting because they needed my buy-in to get some technical work done. The meeting was precisely the disaster I expected. I was expected to read a print-out (I use text-to-voice) in some standard font (I use Open Dyslexic). I was expected to read this wall of text in 20 minutes (I scored in the bottom 3% of the population in reading and retaining information) and offer comments.

Did the Amazon employee ask if this works for me? No. Instead, I was expected to endure. So I did my best. What made it worse was that my other coworkers happily did this work. That was humiliating. I felt I was being denied access and treated as a semi-human being. And I realized I could never work with Amazon as a partner or an employee. And companies would copy this style, and I would be pushed out of those companies as well. And that this megalith of a corporation was about to kick me out of the tech industry. Talk about motivation to make VMware win.

And if I was in a charitable mood at the beginning of the meeting, I was livid by the time we got to my chance to talk. I was like, damn if they are this inconsiderate to partners, I can’t begin to imagine how they treat employees, and I thought – nope, not for me. They came to get my support, and their meeting structure did the wrong thing.

In the end, I was determined to ensure Amazon failed. I wanted them to fail. Because if their success meant more of these meetings, by god, I would do everything in my power to fight back.

I will observe their proposal was ridiculous, and it never went anywhere, more or less for the reasons I described in the meeting. I wasted an hour reviewing a ridiculous proposal and being humiliated.

A win, I guess?

Every so often, someone asks why it is such a big deal, and Sheri Byrne-Haber (disabled) explains it oh so well. Because those meetings are designed to make people like me less effective, I wonder if that’s the intent. But I know me, and mine are not welcome, and I will leave.

Now, I will observe that I had to grow up as well. When I got into a position of power, I, too, wanted meetings that only worked for me. And my team blew a gasket and demanded change, and so I changed begrudgingly. But it was only when I got into a shouting match with a senior executive who wanted the text, not a draining meeting, and we argued. I learned that to be inclusive, I had to accommodate his needs as much as he had to accommodate mine. So I used voice-to-text to produce documents, and he used tools to create text I could process via audio systems.

The point is that any rigid system is a rigid system. And its purpose is to force people to conform and, if that conformance doesn’t work for them, to force them out. And if you want to work with all the best and the brightest, then you need to be flexible and creative and not rely on rigid rules of how meetings must work.

https://www.linkedin.com/pulse/why-amazon-six-page-meeting-process-doesnt-work-sheri/

Share this:

  • Click to email a link to a friend (Opens in new window) Email
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on X (Opens in new window) X
  • Click to share on Tumblr (Opens in new window) Tumblr
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on WhatsApp (Opens in new window) WhatsApp

Like this:

Like Loading...

Filed Under: Uncategorized

A rebuttal of some of the points of Mr. Jassy

February 19, 2023 by kostadis roussos 2 Comments

Note I come to work five days a week. I like being in the office. I enjoy being around human beings. And have been leading remote teams for almost 20+ years. In that time, my groups have delivered over 10 billion dollars in actual money, many multiples of that in shareholder value.

Mr. Jassy wrote this memo to his staff, telling them why he would require everyone to come to work.

Update from Andy Jassy on return to office plans (aboutamazon.com)

So he starts with this:

It’s easier to learn, model, practice, and strengthen our culture when we’re in the office together most of the time and surrounded by our colleagues. It’s especially true for new people (and we’ve hired a lot of people in the pandemic); but it’s also true for people of all tenures at Amazon. When you’re in-person, people tend to be more engaged, observant, and attuned to what’s happening in the meetings and the cultural clues being communicated. 

Except if you have ADD and sitting in a meeting where you cannot sit still gets in the way. Or you are deaf, can’t hear what people are saying, and don’t have zoom translate what is being said in real-time.

For those unsure about why something happened or somebody reacted a certain way, it’s easier to ask ad-hoc questions on the way to lunch, in the elevator, or the hallway; whereas when you’re at home, you’re less likely to do so

I am surprised by this one. The emergence of technology like Slack or the DM function in Zoom has democratized communication. Finding time for a senior leader to ask them a question is tricky. And the senior leader in the elevator can walk away from you. But when you send them a message, they tend to take the time to respond because they can do so asynchronously.

In the more productive brainstorm sessions I’ve been a part of over the years, people get excited and blurt out new ideas or improvements to prior proposals, quickly advancing the seed of an idea, and leading to the broader group getting energized and feeling that it’s onto something. This rapid interjecting happens more often in-person because people feel less inhibited about jumping in or even interrupting sometimes. 

I am a cis-gendered white man at the apex of my profession, which worked for me. How many women and non-white and non-cis-gendered men have we trashed over the years because they didn’t speak up?

My first meeting back in person was the same old guys talking with all of the women and others silent.

It was so bad we had to introduce zoom to deal with the problem.

Serendipitous interactions help it, and there are more of those in-person than virtually

This one surprised me. The number of in-person interactions is an order of magnitude smaller than the interactions with people digitally. Just count the volume of people you contact over email, the number of people your email goes out to, etc. Mr. Jassy feels that is low-value communication.

Regardless, Mr. Jassy has made his choices, declared that he believes they are correct over other people’s lived experiences, and can force his employees to choose to work for Amazon or leave.

Share this:

  • Click to email a link to a friend (Opens in new window) Email
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on X (Opens in new window) X
  • Click to share on Tumblr (Opens in new window) Tumblr
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on WhatsApp (Opens in new window) WhatsApp

Like this:

Like Loading...

Filed Under: Uncategorized

Where else to find me

December 18, 2022 by kostadis roussos Leave a Comment

kostadis_roussos | Twitter | Linktree

Share this:

  • Click to email a link to a friend (Opens in new window) Email
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on X (Opens in new window) X
  • Click to share on Tumblr (Opens in new window) Tumblr
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on WhatsApp (Opens in new window) WhatsApp

Like this:

Like Loading...

Filed Under: Uncategorized

Ubiquity and the ventilator and adding 15 years to everyone’s life

January 13, 2022 by kostadis roussos Leave a Comment

My father is Prof. Charis Roussos. He’s currently 78 years old. And he’s a legendary figure.

To make Prof. Roussos’s impact tangible, let’s compare how set designers imagined the future of hospital medicine.

In 1966, the set designers of the sci-fi show Star Trek imagined the medlab of ~2254 looked like this.


The hospital was a single doctor with a digital chart.

But in 2009, the set designers for the film Star Trek imagined the medlab in 2233 looking like this.

Notice the ventilator, the machines surrounding the hospital bed? Prof. Roussos made them a necessary part of medicine.

But why did this ventilator become so ubiquitous in just 43 years?

Before his research, there was this thing called “shock.” Patients would enter “shock” and die. And the why was a mystery.

But its existence meant that a whole class of things we take for granted are impossible. Surgeries that could save your life but might lead to “shock” were very risky.

But was shock?

He and his teams proved that shock happened when blood pressure dropped.

Let me explain.

Typically you have a specific volume of oxygenated blood pumping through your body. We all know that the heart is a muscle, and we all know about the lungs, but what we didn’t realize was that there were some equally if not more essential muscles, “the lung muscles or the thoracic muscles.”

The body needs oxygen; otherwise, it dies. And without the lung muscles moving, you don’t breathe and die.

But for the lung muscles to move, they need oxygen as well.

Under normal conditions, this is not a problem. There is enough oxygen coming in and enough blood going around for everyone.

But when a patient is under distress, and there is less blood to go around, the brain needs to make some tradeoffs. Well, it can’t stop breathing, so it keeps the lungs working and starves everything else, including itself.

But how much blood do these lungs need? Well, about 25% of the total blood flow.

So what was shock – less blood being pumped through the heart meant less oxygenated blood for everyone, which meant that vital organs started to fail, which led to death. To deal with that, the brain then tells the lung muscles, “WORK HARDER,” and sends even more blood, and the lungs work harder, and vital organs get further starved. . Until they are exhausted, and the brain realize it can do nothing, gives up, and the patient dies.

Shocking.

These lung muscles were the key to keeping people alive!

But how to do that? Well, if the brain only cared about oxygen, what if we fed the patient oxygen or artificially moved the lungs?

And that’s where ventilators come in.

What if we used ventilators to move the lungs artificially, allowing more blood to flow to other parts of the body?

That simple idea saved people who would otherwise have died and enabled surgeries and procedures that in the past were too risky.

You can hear him talk about this here.

Share this:

  • Click to email a link to a friend (Opens in new window) Email
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on X (Opens in new window) X
  • Click to share on Tumblr (Opens in new window) Tumblr
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on WhatsApp (Opens in new window) WhatsApp

Like this:

Like Loading...

Filed Under: Uncategorized

52 architecturalist papers: the different flavors of availability

November 7, 2021 by kostadis roussos Leave a Comment

In a recent sequence of discussions on availability at work, I realized that there are different flavors.

But first, a history lesson.

Before virtualization became a thing, the physical data center physically existed. And its destruction, although possible, was extremely rare.

The destruction of an entire physical data center was extremely rare, and we referred to it as a “meteor strike or nuclear war.”

For practical purposes, availability was about dealing with physical component failures. For example, if a server had a disk, and the disk died, could the application on the server keep running?

As hardware components became increasingly resilient and the cost of hardware plummeted, the weak link became the software.

Because rearchitecting software to become intrinsically highly available was impossible, new software frameworks came into existence.

One of the most impressive was vSphere-HA because it said the following

  1. If you have highly available storage and enterprise storage was highly available
  2. If you have shared storage, and enterprise storage was shared
  3. And you capacity connected to that storage, all of your applications will restart after 5 minutes.

vSphere HA and its more boutique solutions more or less solved the availability problem.

And the power of vSphere-HA to systematically solve the HA problem across an entire application fleet greatly expanded the value of VMware’s technology value proposition.

Except, a new availability problem emerged.

In the past, a single software could not destroy a single data center or all data centers. The scope of the blast radius of an operator error was quite limited.

But with virtualized infrastructures and cloud infrastructure, a single button click can destroy an environment in minutes.

For example, at Zynga, an operator error caused by a lousy user-experience design deleted the production Cityville deployment. Cityville had over 10 million Daily Active Users (DAU) and 30 million Monthly Active Users (MAU).

Why was this possible?

Because in the past, you couldn’t delete a server, the applications in the server, the network connections associated with that server, and the data contained in those servers with a single button click in minutes because it would require logging into hundreds of systems. Why? Because the nature of the systems relied on multiple administrators of infrastructure coordinating to either provision or delete infrastructure.

Let’s use an analogy from social media. Before Facebook, I couldn’t share the news with millions of people using a few button clicks to use an analogy. I had to talk to a lot of people. And so, the blast radius of my news was quite limited. Facebook made it easier to share good information like I have a new child very quickly, and sad news like a friend died very quickly. It also made it possible to share fake news and lies very quickly as well. The same technology could be used to do both. And the societal damage of that rapid dissemination of phony information is confirmed.

Virtualization and later cloud moved the entire data center that the application depended on into a single database. The single database allowed agility to grow, shrink, and adjust infrastructure demand to meet the changing application demand. It also made this database the single most significant vulnerability to your environment.

And so software engineers rightfully focused on how to make that database available. But the problem is that no amount of software available can solve operator error, and worse, mistakes that destroy the database in its entirety.

As more and more effort was put into making the central system more robust and available, the overall design became more and more fragile.

But what kinds of errors? Remember, the physical data center rarely goes away in its entirety, but several servers? Those fail all of the time. Worse, as the servers become less available to become cheaper and more disposable because technologies like vSphere HA or cloud-native 12-factor application styles expand, their failure rate increases.

And this cheaper hardware that is more disposable is possible because of the very same centralized databases that when they fail destroy everything. Antifragility makes it clear that the more and more you make everything depend on a single system, the more and more the entire system becomes fragile.

So we have this peculiar phenomenon that the entire virtual infrastructure of the data center resides in a single piece of software that if it fails, everything is gone. And the thing that can cause it to fail is not under the control of software: things like Human error, or data corruptions in parts of the stack that are unknowable, or ransomware, etc.

Without any personal internal knowledge, the Facebook DNS debacle is a great example. The software allowed the network engineering team to make widespread infrastructure changes across Facebook in minutes. And human error combined with technology errors (just another word for human errors) resulted in the entire Facebook infrastructure is unavailable.

IT operators understand this point, as did DevOps teams and the SRE teams. And this is why they refrain from having a single system control their entire infrastructure. The scope of a single error is why those groups like to have more k8s clusters instead of one large one. Or why backup admins have backup software from a different vendor from their primary storage.

Centralizing things allows for unprecedented agility and failure.

What to do?

My take is threefold.

The first is that the era of centralized databases that control the entire infrastructure is closing. Instead, we will have many databases. In the k8s space, the idea of a few large k8s clusters is an anti-pattern. And this is why I am such a huge fan of products like Tanzu Mission Control. They line up with the future.

The second is that those centralized databases will have to be built leveraging blockchain systems that protect against byzantine errors and, in particular, human errors.

The third is that the ability to recover from those database errors in a timely fashion will become a critical differentiator. A once-in-a-decade event is terrible if it happens on a Friday and a company ending event on Black Friday. Software stacks that make that recovery quick and easy will win.

Share this:

  • Click to email a link to a friend (Opens in new window) Email
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on X (Opens in new window) X
  • Click to share on Tumblr (Opens in new window) Tumblr
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on WhatsApp (Opens in new window) WhatsApp

Like this:

Like Loading...

Filed Under: Uncategorized

Those AI classes turned out to be useful

July 29, 2020 by kostadis roussos Leave a Comment

I sat in a meeting the other day where someone said, “well, computer scientists are obsessed with determinism and refuse to recognize non-determinism.”

And it got me thinking, again, about something I wrote about many, many years ago (2012).

What I wrote was that the history of thought was about moving from a universe where everything was understandable to a world where everything could not be understood. And that article can be found here https://www.forbes.com/sites/quora/2012/06/04/why-would-anyone-want-to-work-for-zynga/#7846a1cb658d. There are a lot of things that I wrote that are embarrassing. I was naive. I was optimistic. And yet, I was right in echoing the thoughts of much smarter people.

Later on, I synced up with an old friend, and we wrote an essay on the limitations of human understanding. That, homo sapiens are inherently limited in their ability to understand the universe. And that limitation makes revelation, the intuition of truth without the ability to prove the truth, not a failure of reason, but an indication of its limits.

And so ten years later, I found myself giving a talk to a bunch of engineers about desired state systems.

The core of the discussion was that planning algorithms that attempted to search a state-space exhaustively were inherently flawed, if the system was exposed to unknown external inputs. When trying to change the state of such a system, if you assume you know how to go from the current state to the desired state, you are wrong because the current state is invalid at the time you made the plan.

30 years ago, I remember sitting in a class learning about planning, and recent research on machine learning, POMDP, and thinking what does this have to do with anything.

It turns out, everything.

Share this:

  • Click to email a link to a friend (Opens in new window) Email
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on X (Opens in new window) X
  • Click to share on Tumblr (Opens in new window) Tumblr
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on WhatsApp (Opens in new window) WhatsApp

Like this:

Like Loading...

Filed Under: Uncategorized

Being a professional and Albert Speer

June 28, 2020 by kostadis roussos Leave a Comment

When I started my career, I was a mercenary. I cared about the money, and the puzzle. I didn’t give a damn about what the stuff I built was used for.

My first job was at SGI, and my first bit of tech helped design stuff at Labs that were so secret that all I knew was that I couldn’t ask any questions. All I knew was that every question was, “I’m sorry we can’t tell you.”

My next job was at NetApp, where I built streaming media caches. The first use of those systems was for porn. The whole point of the internet at that time was porn. I used to find it amusing that I helped people see porn and enjoy porn.

Twenty-one years ago, porn was seen as – well – bad. And being a sex worker was seen as -bad-. And I’ve changed that point-of-view. But back then, I liked being part of the bad industry and being able to claim – like Albert Speer – my position is apolitical.

My mom would ask me what I do, and I would stare at her mischievously and tell her that I helped people.

My line was, “I am a professional. If the problem was how to build baby torture devices, and it was interesting, and the pay was good, I would do it.”

But somewhere, in the back of my head, the story of Albert Speer scared me. See, Albert Speer was the guy a whole generation of Europeans used to justify their silence and blindness in the face of the Holocaust. He was just a technocrat. A man that you could almost admire.

In my head, he was the guy that made the evil possible. He was the representative of the worst kind of human being who was the professional without whom the madmen would never have been able to kill at scale.

One thing about growing up is that you can sometimes have two contradictory thoughts in your head until revelation happens.

In my case, it was a rebirth of my Christian faith. And a realization that being that professional was wrong. That actions mattered.

But revelation and action take a long time.

And over time, I have started to make decisions and choices about who I work for, and where I work based on the principles of the leadership and their willingness to take action on things I care about.

My Christian faith makes it impossible for me to expect Saints, but it also demands that I look for better leaders.

After I left NetApp, I went to Zynga. And there, I discovered Mark Pincus, who, despite all of his flaws, showed that being a principled leader was possible. I won’t forget his decision to insist that the mafia wars design team delete a creepy scene from Mafia Wars II. There were other decisions, but that one still sticks out.

And my personal success makes it possible to take risks, that others can’t.

I don’t want to be Albert Speer.

Growing up, I couldn’t understand how people would worship that man. And the lesson I had learned was that you could have it all if you knew how to ignore the evil you helped create.

He was the consummate professional. And I could have it all if I was like him. I could be a technologist bereft of a moral compass, and have it all.

But I grew up, and in growing up, I became disgusted that I was like him, and I started to change.

In the back of my head, the fact his reputation survived galled me. It meant that amoral professionals never got their due.

It’s with great satisfaction that the latest biographies of Albert Speer, make it clear, he was evil and should have hanged. It’s with great relief, I see his reputation crumble, and the people who fell for him having their reputations crumble alongside him.

It’s 2020, and we technologists enable systems that create harm, like Facebook. Without us, Mr. Zuckerberg could not choose to allow hate to spew. Our systems allow him to make choices that are questionable at best, evil at worst.

And Mr. Zuckberg is not alone. There are others. Our personal morality can not be entirely divorced from our profession. Being a professional doesn’t absolve you from not knowing.

And if we think history will be kind, let’s remind ourselves of Albert Speer. History, was not kind.

Share this:

  • Click to email a link to a friend (Opens in new window) Email
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on X (Opens in new window) X
  • Click to share on Tumblr (Opens in new window) Tumblr
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on WhatsApp (Opens in new window) WhatsApp

Like this:

Like Loading...

Filed Under: Uncategorized

Rage quitting

September 14, 2019 by kostadis roussos Leave a Comment

The only rule in tech is you never, ever, ever, rage quit.

What’s rage quitting?

It’s getting so pissed off, that you walk out the door and take whatever next job you find.

Now, let me point out there are circumstances where rage quitting is the right thing to do, and that’s where there are moral and ethical lines being crossed that you can not abide. Or where someone does something that is truly horrible. I have no experience in those kinds of circumstances, and I offer no useful advice. All I can say is – do what you need to do to be safe, and talk to a labor attorney.

But if you aren’t in one of those really bad places, why is rage quitting a bad plan?

First, it’s a bad plan because your next job is probably not going to be the next job you actually want. And so you’ll be looking for another job pretty soon after that.

Second. it’s a bad plan, because the person who pushed you to rage quit, is forcing you to leave on their terms, not yours.

Third, because it puts you in a vulnerable position. A lot of very bad people can tell if you are the kind of person who will rage quit. They will exploit that, to get you to quit. They will push your buttons, and get you so angry that you will quit.

And they don’t get to run your life, you get to run your life, and surrendering that much control to them is never a good idea.

So you are angry, and furious and pissed off and want to quit, what do you do?

First, take some time off. You can take time off at work, you can take time off at home, you can find the mental space to not be angry. As Joe Beda said, don’t rage quit, rage vacation.

Once you are done with the vacation, then figure out what the right next move is. Be honest with yourself, and determine what you want. In some cases, it’s going to find another job. In other cases, its talk to your boss or his boss about the fact you wanted to rage quit, and see if a change is possible.

But figure that out.

And then go get it.

Share this:

  • Click to email a link to a friend (Opens in new window) Email
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on X (Opens in new window) X
  • Click to share on Tumblr (Opens in new window) Tumblr
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on WhatsApp (Opens in new window) WhatsApp

Like this:

Like Loading...

Filed Under: Uncategorized

They is quitting, and what to do about it

September 9, 2019 by kostadis roussos Leave a Comment

Over the years my teams have gone through waves of attrition. And typically those waves of attrition hit me like a punch to the gut, because every time they have happened, I was asked to do a dive and catch.

I was asked to try and convince someone to not take a job that they had already accepted. And that’s a tough place to be.

And it sometimes worked, but most often did not.

And even it did, they probably quit within 6 months.

And especially for senior people, their departures at critical phases of a project or business was very disruptive.

So if you get int that situation, what can you offer?

1. Offer more money

2. Offer another title

3. Offer time off

4. Offer a new project.

But the problem with these offers is that you are just buying yourself some time. Whatever underlying issues caused the person to quit will resurface after 6 months.

And what really upset me was that I was always felt they were leaving, not going. That we failed to show them the opportunity and deal with their real legitimate grievances.

So why bother? Because you get six months to figure out, on your terms, what the transition plan should be.

And that brings me to what you actually have to do.

From painful personal experience, I learned that 1×1’s are the best path to ensuring that folks are feeling connected to the organization.

The more 1×1’s you have across the org, the more people are connected to the team, the more you can deal with problems earlier rather than later.

Sometimes people leave, and that’s okay. Change is not a bad thing. But you owe it to your team for them to feel that there was a better opportunity somewhere else, and that they are not fleeing a bad place.

And so in my latest gig we mandated that our teams and leads do 1×1 and report the number of 1×1’s. And our attrition rate dropped to historic lows. Yes, part of it was the awesomeness of the Project Pacific, and our stock price, and part of it was that folks were feeling very connected to the mission as a whole.

And I am doing a lot fewer dive and catches these days….

Share this:

  • Click to email a link to a friend (Opens in new window) Email
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on X (Opens in new window) X
  • Click to share on Tumblr (Opens in new window) Tumblr
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on WhatsApp (Opens in new window) WhatsApp

Like this:

Like Loading...

Filed Under: Uncategorized

12 architecturalist papers: people write software

May 30, 2018 by kostadis roussos Leave a Comment

When I first became an architect at NetApp, I thought the job was to draw a picture, get the picture approved and then the software would magically be written.

The mental model I had was that there was this massive “power-point to product” compiler and all I had to do was draw the power-point.

To my surprise, it was a little bit more complicated.

People write software, and people are not computers. People have emotions, aspirations, interests, career goals, dislikes, strengths and weaknesses. And those people write software.

How does this influence software system design?

In the first phase, you need to figure out what the right system is. Correctness or appropriateness of a system is independent of human beings.

But then to get it implemented, you need to understand your team.

There will be skills your team has, and there are skills your team needs to acquire and there are skills your team lacks and can’t learn and you need to go find in the marketplace.

And then your job, as a systems architect, is to figure out how to build something with the people you have that adds enough value so you can stay alive.

And sometimes it means you have to wait to hire the people you need.

In many ways, this process feels like being an author of a screenplay who tailors the screenplay to the actors you hired.

One of my projects at Zynga could not start until I hired someone who understood filesystems. And so I lived with data corruption and inconsistency because there was no one who could fix the problem. And when that person was hired, I had to wait for them to ramp up at Zynga. And when they finally ramped out, only then could I actually get them to work on the problem.

But finding the right person to solve a problem is the easy part of the job. Motivating them to solve the problem is the hard thing.

The really hard part is to motivate people to write the software. Remember people have lots of reasons why they do things. And people’s best work is done when they are fully engaged in a problem, when they show up wholly – mind and heart and body.

You don’t want extrinsic motivation, because you don’t get people’s best work.

And that means a bunch of things.

The simplest and most obvious is that people have to feel safe to be themselves. If people don’t feel safe, then they will not be there. They have to feel supported. They have to feel free to be their authentic self.

Screaming at people, dismissing people, being cruel, demonstrating how much smarter than them you are, trashing their work, is how you get something other than their best work. And sadly in my past lives, I had to have a boss explain this very simple thing to me. And I’ve had to be reminded of this on more occasions than I like.

The second is that they have to feel that what they want will happen. And what they want is not what you think it is.

A large part of the job as an architect is to spend time 1×1 with everyone and making sure that they are wholly engaged. And understand what they need. And everyone is different.

For example, a co-worker of mine was trying to re-architect a system, and he was running into flak from his team. And I asked him: Did you talk to everyone to see what they wanted from this effort? And he said, no. And I said: How can you convince people of something if you don’t know what they want?

So he scheduled a bunch of 1×1’s, found out what everyone wanted, and all of a sudden the flak evaporated. It didn’t evaporate because he listened to people, the flak evaporated because he adjusted his plan to meet their wants and needs.

Sometimes I get asked: Why do you spend so much time talking to people? And my answer is: People write software and I want people to be fully invested in a solution because that’s how they do their best work.

Do I always succeed? No. But it’s my North Star.

Share this:

  • Click to email a link to a friend (Opens in new window) Email
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on X (Opens in new window) X
  • Click to share on Tumblr (Opens in new window) Tumblr
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on WhatsApp (Opens in new window) WhatsApp

Like this:

Like Loading...

Filed Under: Architecturalist Papers, Uncategorized

  • 1
  • 2
  • 3
  • 4
  • Next Page »
 

Loading Comments...
 

    %d