nibblebit

joined 1 year ago
MODERATOR OF
[–] nibblebit 3 points 1 year ago* (last edited 1 year ago) (2 children)

Let's try a discord first so that we can at least connect and figure the rest out -> https://discord.gg/T4PjRWSa

[–] nibblebit 3 points 1 year ago

Haya! This place looks perfect! I've been using Godot for about four years now for all kinds of forever projects in 3D. Right now, however, I am spending time on a small 2d digging mechanic with dynamic lighting. I'm excited to start using the new multi-window feature for some fun stuff.

[–] nibblebit 2 points 1 year ago (1 children)

The price of perfection is infinite. It's not about structuring everything, and it doesn't have to be top-down. But, at some point, a team grows to more than ten people, and it's not enough to self-structure. At some point, you must agree on who is responsible for what instead of everyone being accountable for everything.

I agree with you on all points as to desired outcomes. I think it is particularly interesting that you emphasize how important vision is. I have found it difficult enough to have a medium-sized organization even come up with a vision, let alone effectively communicate long-term, medium and short-term plans to engineering teams. Aligning projects with goals and setting milestones is a great way to communicate a vision. I've found it tricky to use metrics to track progress or performance. Do you have any ideas about how to use metrics to help align with a vision?

[–] nibblebit 2 points 1 year ago

I'll start with one of my favourite classics: Enterprise integration patterns - Gregor Hohpe and Bobby Woolf

Truly the final word in messaging systems and required reading for any cloud architecture where you are having multiple services talk to each other at scale.

[–] nibblebit 2 points 1 year ago

Wonderful! thanks :)

[–] nibblebit 6 points 1 year ago (2 children)

Hello!

I'm an Azure/dotnet dev and I am bad at Powershell. I am looking forward to sharing all of my disgusting hacks with you all!

[–] nibblebit 2 points 1 year ago

Article is a bit dated and hard to read. The gist of the author is relatable though 15 years later: redundancies have been hella annoying, especially if they are unknown. Bad abstractions, however, create dilemmas, dead-locks and chicken-and-egg situations. And it's impossible to create good abstractions unless you have no colleagues and no customers.

I would take some frustration over grinding to a halt any time.

[–] nibblebit 7 points 1 year ago (3 children)

Can we have a general cloud engineering community? Something encompassing the Azure/AWS/GCS and others for news, Instructables etc. /c/loud would be perfect :)

[–] nibblebit 6 points 1 year ago (3 children)

it must be /c/sharp I would not have it any other way

[–] nibblebit 8 points 1 year ago* (last edited 1 year ago)

IT operators and DevOps engineers have been a nightmare liability for security, governance and business continuity. The best-case scenario for a DevOps/IT operator is that you get a superhero that does everything and knows it all. All responsibilities and security privileges gravitate towards this role, and knowledge sharing becomes impossible. Lastly, it becomes impossible to track the thousands of out-of-band changes initiated by a DevOps team to an auditor or certifier.

Cloud engineering, feature management and IAC tools have made it way better for engineers to build and deploy self-monitoring systems. A modern software ecosystem can be deployed, updated and migrated on an automated schedule. It can be done, safely without any of the responsible engineers having direct access to environment secrets or sensitive data. All of these changes can be set under version control for auditing purposes. If given the option, any smart employer would prefer the option to invest in such a system rather than support a 24-7 response team.

There will always be a need for surgery on a production environment, but there's no reason that can't be a formalised incident. If you are having weekly incidents that require engineers to do operations work, then that's something that needs to be addressed.

We should all be working to eliminate operations work. IT operator needs to be a trusted security role, not a critical glue with all the keys that holds a system together.

[–] nibblebit 5 points 1 year ago* (last edited 1 year ago)

Hey! Wonderful place!

I bet the server costs will hockey stick the coming weeks. It will probably not cool down soon, especially if you need CSAM moderation.

Is there any place we can contribute monetarily? I would be happy to pitch in to a Patreon or Mollie sub something.

Additionally, is there an IRC/Discord or something for the community?

view more: ‹ prev next ›