@kenny.weave-it.org do you have experience with using collaborative modeling for embedded systems? I am looking for the right format to align a couple of teams from hardware to cloud but it is not a straightforward process, so Event approaches seem inadequate.

there is a certain comfort in formulaic development "well, today I will do the entity classes, tomorrow the repository and after that the controller and service" but if something is formulaic maybe it should not be done manual at all

the fastest horse in the feature factory

I have been informed that "data platform" means "chaining together data lakes and spark jobs" for many people funny how you can skip all of pythons ecosystem when instead your platform only does ingest and retrieval (and absurdly complex non-numeric processes)

long-term I want to be working on developing infrastructure or other technically challenging topics, so I have finally bit the bullet and am learning Rust it's crazy how much easier it is this time around now that writing high perf go has made me memory and pointer sensitive

I am wondering under which circumstances the uniqueness probability of UUIDs is not enough, defense tech?

nothing worse for my motivation than a project without urgency either make it count for something or at least pretend and put us on some good old dev cycles

migrating a large scale streaming platform without downtime is quite difficult

Only 30% of developers collaborate with colleagues on features, can that be true?

Lucca@luccahellriegel.com · 2y ago

I did a little survey back in January with dismal results (maybe bad phrasing?)

I have less than zero interest in working in business software again if collaborative modeling is not a regular part of the process alignment, knowledge, communication are most of the problem to be solved, why are we making it hard? building another context-less endpoint is not the juice of life

I have not met any k8s-as-code deployment tool that I didn't hate sooner or later

I would rather firefight in a project than feel like it doesn't matter

working on legacy code is often just a long time of gradual improvements but it also affords a unique opportunity to see the effects of year-old decisions future-proof decisions are supposedly a hallmark of quality but most people leave before they see how it pans out, how can they learn?

bsky still seems to be in the "sub4sub" stage, old youtube homies remember

theblueskymagean is here

brb calling my mum to tell her she severly handicapped my career by limiting my play time as a child

Why@why.bsky.world · 3y ago

Send us your resume if you: - Can code - Played over 1000 hours of factorio - Think social media could be better

I should get someone here to ban me. but not enough coffee for that

at this point I only want a new job if it absolutely terrifies me. gotta live bro

either I learn Go or I Go learn Rust.

Did the thing with domain. I knew at some point it would be useful to own my name