New google service that creating UI from text
https://stitch.withgoogle.com

Друзі, нажаль мій контракт не поновили. А це значить, що я не взмозі платити за 200+ хворих тварин в наших притулках.

Я не знаю скільки піде на пошук нового клієнта, але зараз ваша допомога вкрай потрібна.

Наразі в нас ~500к грн боргу який немає чим закрити.

Я довгий час закривав це своїми коштами та боргами, але зараз ми цілком залежимо від вашого розуміння, довіри та бажання допомогти тваринам.

🎯 Зібрано: 44к/500к

https://uah.fund/donate

Тако ж нагадую, через фін проблеми, які тільки погіршились нам потрібно закрити другий притулок. А для цього роздати 100 тварин.
І якщо раніше в мене був бекап, зараз його немає. Тварини без підтримки загинуть. То ж якщо хочете стати родиною для пухнастика пишіть мені.

Тако ж якщо в вашій компанії є вакансії які матчаться з моїм досвідом, то буду дуже вдячний за рекомендації та шер мого профілю з вашими колегами https://www.linkedin.com/in/creotiv/

Question for DevOps: Are you building top level components in #Terraform?

Usually i see that for every application DevOps are building full config based only on low-level components. Which makes these configs pretty big, and impossible to maintain them by developers(for example when they need to deploy new service fast).

In my work i came to the same solution like in #UI building, by creating top level components that remove all these scary things from developers and give them simple #UX to work with.

For example we have many different services and all of them may use standard aws components like db, cache, gateway, lb, etc. So i build component where we can just select what we will need for a new service and it will be created automatically, even with the ability to run migrations if needed.

From one side this limit what they can do, but from other helps for many similar services. So I'm interested in what you think about such an idea?

Новая модель от Гугл, работает на любом девайсе с всего 2гб оперативки

https://developers.googleblog.com/en/introducing-gemma-3n/

Друзі буду дуже вдячний за репост поста
https://www.linkedin.com/posts/creotiv_friends-im-currently-looking-for-a-new-activity-7332685780118552577-iQef?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAPl0X4BWZSqccqAVcirdBAwe5jWKVOQ9fI

Прикольна апка для перевірки рівня англійської
https://smalltalk2.me

А ви замислювалися про те, що рано чи пізно кар'єрі прийде кінець а жити якось далі треба буде?

Прошу до обговорення
https://www.linkedin.com/posts/creotiv_any-software-engineer-can-experience-a-activity-7334669130991591424-Taj0?utm_source=share&utm_medium=member_android&rcm=ACoAAAPl0X4BWZSqccqAVcirdBAwe5jWKVOQ9fI

мл локальные модели для андроид
https://github.com/google-ai-edge/gallery

На моєму досвіді, дуже поганою ідеєю є не встроювати обсервабіліті в сервіси з самого початку, бо потім це коштуватиме дуже дорого, а тако ж є багато шансів що до цього моменту компанія просто недоживе

Прошудо обговорення
https://www.linkedin.com/posts/creotiv_when-building-new-software-most-companies-activity-7335021862457917440-yceS?utm_source=share&utm_medium=member_android&rcm=ACoAAAPl0X4BWZSqccqAVcirdBAwe5jWKVOQ9fI

https://www.linkedin.com/posts/creotiv_when-building-new-software-most-companies-activity-7335021862457917440-yceS?utm_source=share&utm_medium=member_android&rcm=ACoAAAPl0X4BWZSqccqAVcirdBAwe5jWKVOQ9fI

🏭 I built a small #tutorial that illustrates how sidecar containers can transform observability and control in any Kubernetes‐based service. Instead of embedding metrics, logging, and networking logic directly into your app, you simply “bolt on” three dedicated sidecars:

1. Prometheus – Collects application and infrastructure metrics out of the box.

2. Promtail → Grafana Loki – Streams logs in real time without changing your app code.

3. Envoy Proxy – Handles TLS termination, request filtering, and even simulates network failures.

✅ Why this Matters

- Separation of Concerns: All observability (metrics + logs) and networking (TLS, filters, chaos testing) live outside the main container. Your app stays lightweight and focused solely on business logic.

- Consistency Across Services: You can reuse the exact same Prometheus/Promtail/Envoy configuration for every microservice. No more “one‐off” instrumentation code in each repo.

- Faster Development & Onboarding: Developers don’t need to spend time wiring in monitoring libraries or custom proxy code—sidecars handle it for you automatically.

- Easier Upgrades and Troubleshooting: When you need to tweak logging formats or experiment with TLS settings, you update the sidecar image, not dozens of disparate applications.

⚠️ Considerations

- Resource Overhead: Each sidecar adds CPU/memory usage. In lightweight deployments, be mindful of your node capacity and pod limits.

- Operational Complexity: More containers per Pod means more YAML to manage and additional network hops. You’ll need to ensure your CI/CD and Helm charts stay up to date.

- Sidecar Lifecycle: When you roll out a new version of your app, the sidecar versions may need to stay in sync (e.g., Promtail pipelines). Establish clear versioning and testing practices.

Ultimately, moving observability and networking logic into reusable sidecars makes your main application image lighter, speeds up developer onboarding, and enforces a consistent control plane across all services. If you’re evaluating how to standardize monitoring, logging, and network policies at scale, consider a sidecar‐centric approach. It’s a small shift in architecture that can pay big dividends in maintainability and speed.

https://github.com/creotiv/sidecar-demo

Якщо комусь цікаво що і як в зооволонтерстві
https://www.youtube.com/watch?v=hZbDCemx_oY

Погоджуєтесь?

https://www.linkedin.com/posts/creotiv_almost-every-software-project-needs-a-activity-7335986435101011968-LE1y?utm_source=share&utm_medium=member_android&rcm=ACoAAAPl0X4BWZSqccqAVcirdBAwe5jWKVOQ9fI

як за 5хв написати модератора для ютюб стрімів

https://www.linkedin.com/posts/creotiv_people-saying-vibe-coding-is-a-bad-thing-activity-7336053511316455426-VzAF?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAPl0X4BWZSqccqAVcirdBAwe5jWKVOQ9fI

Modern generative #AI and large language model (#LLM) services create unique traffic-routing challenges on #Kubernetes. Unlike typical short-lived, stateless web requests, LLM inference sessions are often long-running, resource-intensive, and partially stateful. For example, a single #GPU-backed model server may keep multiple inference sessions active and maintain in-memory token caches.

Traditional load balancers focused on HTTP path or round-robin lack the specialized capabilities needed for these workloads. They also don’t account for model identity or request criticality (e.g., interactive chat vs. batch jobs). Organizations often patch together ad-hoc solutions, but a standardized approach is missing.

And here comes the new #Gateway API Inference Extension in #K8S

https://kubernetes.io/blog/2025/06/05/introducing-gateway-api-inference-extension/

Bonhoeffer’s Theory of Stupidity: A Tool for Control?

Dietrich Bonhoeffer, a theologian executed for resisting the Nazis, had a haunting insight: stupidity is more dangerous than malice. Why? Because stupid people can be manipulated without knowing they’re being used — and worse, they often become fanatically loyal to ideas they don’t understand.

Bonhoeffer observed that stupidity is not a lack of intelligence but a moral failure, a refusal to think critically. And this, he warned, flourishes most in times of social upheaval and under authoritarian regimes.

Why does this matter today?

Because those in power — whether governments or media empires — often rely on this passive obedience. It’s easier to rule a population that feels informed but doesn’t question narratives, doesn’t challenge contradictions, and fears being isolated for thinking differently.

True resistance doesn’t always start with shouting — it starts with thinking. And that’s exactly what oppressive systems try to prevent.

Bonhoeffer’s warning wasn’t just about Nazi Germany. It’s about every society that starts silencing thought under the guise of unity or safety.

Critical thinking is not rebellion — it’s responsibility.

Watch this video to not regret later
https://youtu.be/Sfekgjfh1Rk?si=kWTd2r7OH8tqwCxT

🔥 Немного про Sidecar контейнеры. Плюсы и минусы использования. А так же как делать системы с которыми просто и приятно работать

https://youtube.com/live/QIIf45UYJM4

Для модерации стрима был использован этот бот
https://github.com/creotiv/youtube-llm-moderator

полайкайте кому не впадло
https://www.linkedin.com/posts/creotiv_%D1%88%D1%83%D0%BA%D0%B0%D1%8E-%D0%BD%D0%BE%D0%B2%D1%96-%D0%B2%D0%B8%D0%BA%D0%BB%D0%B8%D0%BA%D0%B8-%D1%82%D0%B0-%D0%B4%D0%BE%D1%81%D1%82%D0%BE%D0%B9%D0%BD%D0%B8%D1%85-%D0%BB%D1%8E%D0%B4%D0%B5%D0%B9-activity-7339621424090808320-V2C3?utm_source=share&utm_medium=member_android&rcm=ACoAAAPl0X4BWZSqccqAVcirdBAwe5jWKVOQ9fI