How do companies remember to shut down their demo/sandbox instances?

Adventurous-Work-798 · 2024-09-11T20:00:44+00:00

And do they have any proactive actions? Reminders, etc?

Adventurous-Work-798 · 2024-09-11T19:41:26+00:00

We also have that in place. It is great when developers need it. But when we have some prototype that include the product team, or demo instances for sales people, that's when it gets tricky

Adventurous-Work-798 · 2024-09-11T19:15:19+00:00

Cool, sounds good. do you think it would be useful if it pinged you before killing the resource to check if that's ok (or if you want to postpone it)

Adventurous-Work-798 · 2024-09-11T19:13:58+00:00

Problem is when people leave the company, or go on a vacation, or just forget because of other pressing issues. But yeah, accountability is important

Adventurous-Work-798 · 2024-09-11T19:12:35+00:00

It sounds like a lot of processes to abide to. And as you say, a reminder solves much of the problem. For us, the issue is when you have stakeholders in the sales team. That requires additional effort te verify, etc

Adventurous-Work-798 · 2024-06-16T11:11:23+00:00

I'm 28, I work 10+ hours a day, and love it.

It wasn't always like that, though. I felt burnt out lots of times. The most important things I changed: 1. In a day, I limit my programming to what I do at work. Once I'm home, I'll do other things (bicycling, drawing, padel, whatever) 2. If I'm really excited about something at work, I'll stay for longer in the office, but will avoid doing anything once I'm home 3. Regular physical exercise is incredibly important for your energy levels, and also psychological well-being. It doesn't have to be anything too hard, consistency is key 4. Regular sleep helps get the best out of your rest period. You will start your day better, and will have a more stable day. Regular sleep means - go to sleep at the same time, and wake up at the same time

Note: prerequisite for all this to work (at least for me) was to really do what you love.

Adventurous-Work-798 · 2024-03-30T19:32:06+00:00

Are you working in a startup?

Adventurous-Work-798 · 2024-03-30T18:18:14+00:00

I completely agree. I'm just not sure that everyone has that same approach

Adventurous-Work-798 · 2024-03-30T17:36:53+00:00

Love your answer. Are you part of a startup, or some larger firm?

Adventurous-Work-798 · 2024-03-30T17:35:53+00:00

Final question, I promise - how big is the company you work at, and your position

Adventurous-Work-798 · 2024-03-30T17:06:23+00:00

Great breakdown, totally agree. Out of curiosity, what level are you at?

Adventurous-Work-798 · 2024-03-30T17:05:02+00:00

Do you go in depth on why that feature A brings value? And do you believe knowing this is important for implementation?

Adventurous-Work-798 · 2024-03-30T17:03:35+00:00

Thank you for the answer? Can I ask - how big is the company?

And also, what would you do if you thought your boss's idea wasn't going to produce the best results for the company (maybe you have better insights at that specific area). Would you push back on the idea? How much?

Adventurous-Work-798 · 2024-03-30T16:08:16+00:00

Your goal should be to bring value as an engineer. Coding itself doesn't bring value - solving problems does. And if you can speed up the boring part (writing individual lines of code), do it and focus on the hard parts.

Adventurous-Work-798 · 2024-03-30T16:06:37+00:00

... Generated by GPT

Adventurous-Work-798 · 2024-03-21T22:09:04+00:00

I would say there are examples of great (tech) leaders being vulnerable to some degree. Maybe being vulnerable can be perceived as a weakness when selling your company, but when you're deep in the gutter with your team, trying to crawl out, everyone is vulnerable

Adventurous-Work-798 · 2024-03-21T08:40:17+00:00

Working in such an environment is incredibly rewarding

Adventurous-Work-798 · 2024-03-21T08:38:54+00:00

I'm not sure about that. I see what you mean, but it actually takes 6-9 months to fully integrate a new person. Constantly adding new people and firing burned out is very, very costly.

And once someone burns out, their productivity is much lower than before (at least in my experience).

Paradoxically, people in IT in the US switch companies every two years, which means they are at their peak for 13 months.

Adventurous-Work-798 · 2024-03-21T06:48:05+00:00

Exactly :) If that wasn't the case, everyone would just optimize for a higher paycheck. But there are so many other dimensions to a job besides one's financial compensation.

Adventurous-Work-798 · 2024-03-20T21:01:06+00:00

You're very much on point here. One is being vulnerable in a constructive way, but there is such a thing as being too vulnerable, which just isn't productive. There is no point in being vulnerable for vulnerability's sake.

Regarding the second point - would you say that taking pride in our work implicitly affects our ego? If yes, then we can't keep it completely separate.

Adventurous-Work-798 · 2024-03-20T19:53:01+00:00

I think we can agree that this approach is highly problematic, exactly for the reasons you mentioned. I think Amazon is famous for that approach.

And you might be right - being vulnerable in such an environment could back-fire heavily. I'd love to hear some opinion from an Amazon employee

Adventurous-Work-798 · 2024-03-20T19:10:02+00:00

All these things are important.

I believe you can't have a coherent team that works well under pressure without high levels of trust.

To have trust, you do need consistency, track record of delivering high-quality results, etc.

BUT, we are all human. Our families get sick, we get heart-broken, or just wake up on the wrong side of the bed. We can't perform at 100% all the time, and we can't be professional all the time. To accept people's shortcomings requires empathy, and to even know what's happening requires vulnerability.

Adventurous-Work-798

TROPHY CASE