orchunkolcu's profile picture. @orchun@hachyderm.io
Software Engineer, .NET, ponderer of maintainable designs.

Orchun Magnus Kolcu

@orchunkolcu

@[email protected] Software Engineer, .NET, ponderer of maintainable designs.

You might like
Orchun Magnus Kolcu reposted

10 years ago today @aaronsw took his own life after overly aggressive prosecution. He invented internet infrastructure. He defeated the greatest threat the Internet had ever seen. And you probably don't know who he is. You should. Here’s his story 🧵

Patticus's tweet image. 10 years ago today @aaronsw took his own life after overly aggressive prosecution. 

He invented internet infrastructure. 

He defeated the greatest threat the Internet had ever seen.

And you probably don't know who he is.

You should.

Here’s his story 🧵

Orchun Magnus Kolcu reposted

Orchun Magnus Kolcu reposted

So to help with the oil/global warming crisis we're going to destroy marine life in order to build electric cars? Maybe cars just need to go away. theverge.com/2022/7/7/23198…

theverge.com

Mining the deep sea for battery materials will be dangerously noisy, study finds

Efforts to raid the seafloor for metals could kick off next year.


What is the most important thing that will get you out of the trap, assuming sprints and tickets remain constant? - Stop queuing tickets for beyond next sprint? - Promote product engineering & dev autonomy? - Allow slack for better execution? - Call your shots vs "commitments"?

I see people dumping on it a lot but they usually call it “scrum” (or worse “agile”), even though that’s not what it is. I don’t currently have links handy though. How about we report them as we find them with a hashtag?



The reason this isn't painfully obvious is the rejection/correction loop is often swept under the carpet by rubber stamping in reviews.

The mobs tend to make better decisions, and go through the system to production on the first try, instead of writing code that bounces around in rejection/correction loops. As a result, the time to complete is pretty similar, but the time to deploy is much shorter.



A dead giveaway is when they start talking about CI and TBD as different concepts.

Folks toss around the "CI" term but mostly in regards to tooling. I get the sense that most teams aren't actually continuously integrating. Better question, do folks actually know what CI is?



United States Trends

You might like

Loading...

Something went wrong.


Something went wrong.