Software engineer that loves to write about quality and clean code. "The road to software hell is paved with bad code." https://xitter.cf/t.co/Hw4T6CmswP

North Macedonia
Joined April 2016
Aleksandar Bako Markovski retweeted
Replying to @opentelemetry
@opentelemetry is officially a CNCF graduated project! 🎓🎉 OpenTelemetry has become the trusted de facto observability standard, backed by 12,000+ contributors from 2,800+ organizations and helping teams gain better visibility across distributed systems. Congrats to this incredible community! Read more about the milestone here: bit.ly/4fvcHAb
2
67
6
249
36,071
Aleksandar Bako Markovski retweeted
2
2
1
3
199
Aleksandar Bako Markovski retweeted
NEW POST Conversations with AI are ephemeral, decisions made early lose attention as the conversation continues, and disappear entirely with a new session. @techygarg explains how to externalize the decision context into a living document. martinfowler.com/articles/re…
14
47
5
405
83,941
Aleksandar Bako Markovski retweeted
Kubernetes 1.36 launches April 22, marking a major shift in networking as Ingress-NGINX retires in favor of the more scalable Gateway API. Key updates include bolstered Linux user namespaces for better isolation and Dynamic Resource Allocation (DRA) enhancements for hardware maintenance. Read the full breakdown 👉 buff.ly/6NzITIW #Kubernetes #CloudNative #K8s #GatewayAPI
2
2
450
Aleksandar Bako Markovski retweeted
Folks, I'm looking for @openclaw maintainers. If you love open source, have experience with running larger projects, are security minded and want to help, drop me an email. github.com/openclaw/openclaw…
336
459
75
6,206
441,086
Aleksandar Bako Markovski retweeted
We need new societal rules and likely new laws for AI agents acting on behalf of humans in the real world. There needs to be accountability, a shared code of conduct, and some basic common sense when releasing agents into the wild. To be clear: I'm a techno-optimist and I believe AI belongs in everyday life and that technological progress should continue. AI should be built and especially deployed responsibly. Releasing systems that can touch real infrastructure, private emails, phone numbers, financial accounts, or machines is serious, especially when done carelessly and at that point, you are delegating real power, often while hiding behind the identity of an agent. That kind of power requires accountability. We're starting to see more people deploy agents with limited experience, weak operational discipline, and no ownership over outcomes. It's funny until it isn't. We need clear responsibility for agent actions. We need traceability of who deployed what and with which permissions. We need liability when agents cause harm. We need guardrails that scale with capability. Vibe responsibly!
1
1
2
196
Aleksandar Bako Markovski retweeted
2025 was a big year in tech, and for early career professionals just joining the industry, keeping up with all the newest innovations can be difficult. That's why we've wrapped up the year in tech! Our resident Gen Z expert Phoebe Sajor gives the lowdown on everything Zoomers should know about the tech world now, and the trends to look out for in the year ahead. stackoverflow.blog/2026/01/1…
2
6
2,047
Aleksandar Bako Markovski retweeted
Think of all the most innovative cultures. What do they all have in common? Cold seasons. You cannot afford to be lazy in a cold, seasonal climate: - You can’t live impulsively. If you don’t stock food or plan winter shelter, you’re dead - You must cooperate, or you’re dead - You must delay gratification, or you’re dead - You must create tools, preserve food and build storage systems, or you’re dead Lazy, shortsighted behavior is punishable by death. Cognitive load increases and forward thinking becomes a selective breeding trait. The closer to the equator you are, the less change there is. Resource abundance and constant climate mean no pressure to innovate, no long-term planning requirements. Warmth means comfort and comfort means complacency (biologically speaking). Seasonal cognition is what led to the invention of calendars, agriculture and scheduling. The environmental force that paved the way for: - Industrial revolutions - Scientific method - Modern infrastructure Innovation thrives where the future is uncertain and immediate gratification is punished. Future orientation is an environmental phenomenon.
859
1,348
323
9,967
1,392,696
Aleksandar Bako Markovski retweeted
Get 10,000 free tokens on signup to run the latest GPT-5 models!
This quoted post is unavailable.
1
1
137
Aleksandar Bako Markovski retweeted
😂
1
3
149
Aleksandar Bako Markovski retweeted
vibe coding, where 2 engineers can now create the tech debt of at least 50 engineers
165
1,424
153
14,410
647,951
Aleksandar Bako Markovski retweeted
Macro data refinement 🫨
3
20
1
113
6,655
Aleksandar Bako Markovski retweeted
Big news for #DevOps! Semaphore has gone open source, offering a flexible, scalable CI/CD platform under Apache 2.0. No more black-box pipelines—developers now have full visibility & control. See what this means for software delivery: buff.ly/ZXmcwZu #CICD #OpenSource
2
2
399
Aleksandar Bako Markovski retweeted
🚀 Building an Internal Developer Platform (IDP) doesn’t have to be complex! Join us on March 26 to learn how to accelerate infrastructure provisioning, enable self-service deployments, and maintain governance & cost control. hubs.ly/Q03c7LZB0
1
4
459
Aleksandar Bako Markovski retweeted
You will never refactor or write tests until you have convinced yourself that it’s the most productive strategy. Once you accept that, you won’t need management to give you time because you will be working the fastest way possible. Refactoring _saves_ time. Tests _save_ time.
39
69
11
576
24,835
Aleksandar Bako Markovski retweeted
A team who allows messes to persist in their code will gradually slow down to a tiny fraction of their potential productivity. I’ve seen teams that have expanded their estimates out to weeks and months for jobs that ought to take a day or two. The slower the team goes, the more the pressure builds. The more the pressure build the more messes are left uncleaned. Each such mess impedes the team even more; and the slower they all go. It’s a vicious cycle, and if you’ve been a programmer for more than a couple of years you’ve likely taken a few turns around it. But it gets worse. Managers, desperate to increase productivity, hire new people. This, of course, has the opposite of the desired effect. The new people, thrown into the mass of messy code, see how things are done around here and — of course — they emulate it. So now there are even more people making messes, which drives the cycle even faster, and drags the productivity even lower.
33
71
12
529
30,866
Aleksandar Bako Markovski retweeted
Dear Programmers. Turing called us: “Mathematicians of ability”. He wasn’t wrong; but he missed something. We are not _just_ mathematicians, we are also scientists. Mathematics is a discipline of logic and reason, and every programmer must be adept at those things. But programmers must also base their conclusions on experiential observation. We create hypotheses and then test them experimentally. We are mathematicians and scientists of ability. We have a word for mathematical scientists. We call them: Engineers.
27
70
10
465
27,930