• Wprowadzenie: Film przedstawia ranking 15 popularnych suplementów diety, podzielonych na cztery grupy w zależności od ich udowodnionej skuteczności i uniwersalności zastosowania [00:00:40].

• GRUPA 1: Warto przyjmować codziennie

  • Omega-3 (EPA i DHA) – z uwagi na szerokie korzyści zdrowotne i rzadkie spożywanie ich źródeł w diecie [00:19:41].
  • Witamina D – uznawana za hormon, jest kluczowa z uwagi na jej wielokierunkowe działanie i powszechne niedobory (większość osób w Polsce ma jej zbyt niski poziom) [00:20:20].

• GRUPA 2: Szeroki, korzystny wpływ na zdrowie

  • Cynk
  • Magnez (wskazany ze względu na to, że Polacy spożywają go o 20-30% za mało) [00:13:44].
  • Witamina C
  • Błonnik pokarmowy (większość Polaków spożywa go za mało, choć jest powszechny w żywności) [00:16:56].
  • Probiotyki (ważne dla regulacji pracy jelit, odporności, a także w łagodzeniu objawów depresyjnych i usprawnianiu mózgu) [00:18:32].

• GRUPA 3: Potwierdzona skuteczność, ale wąskie zastosowanie

  • Preparaty wysokobiałkowe (np. odżywki białkowe) – przydatne dla osób aktywnych fizycznie, budujących masę mięśniową, w rekonwalescencji oraz dla osób starszych zagrożonych sarkopenią [00:07:45].
  • Kreatyna – wspomaga wzrost masy i siły mięśni, wzmacnia kości, poprawia sprawność umysłową i pamięć [00:08:40].
  • Melatonina – ułatwia zasypianie, a także łagodzi objawy refluksowe i może obniżać ciśnienie tętnicze [00:10:32].
  • Kolagen – poprawia kondycję stawów, skóry, wzmacnia kości i naczynia krwionośne [00:11:42].

• GRUPA 4: Znikoma skuteczność działania, niepolecane

  • L-Karnityna – jej efekt odchudzający jest marginalny (ok. 1,1 kg redukcji masy ciała w ciągu 8–30 tygodni) [00:01:56].
  • Buzdyganek naziemny (Tribulus Terrestris) – nie ma solidnych dowodów na to, że podnosi poziom testosteronu u większości osób [00:02:50].
  • Woda alkaliczna – promowana głównie marketingowo, organizm sam reguluje równowagę kwasowo-zasadową [00:03:30].
  • Wapń – suplementacja u dorosłych i starszych ma niewielki wpływ na gęstość kości, a może nieść nieznaczne ryzyko dla układu krążenia [00:05:06].

• Tajemnicza substancja BDNF: Kluczowym elementem chroniącym mózg jest BDNF (neurotroficzny czynnik pochodzenia mózgowego), białko działające jak „naturalny nawóz” dla komórek nerwowych [00:00:55]–[00:01:13].
• Wytwarzanie nowych komórek: BDNF stymuluje powstawanie nowych komórek nerwowych i połączeń, zwiększając sprawność umysłową, pojemność pamięci i odporność na zmiany neurodegeneracyjne [00:00:24].
• Mniejsze ryzyko demencji: Wyższy poziom BDNF we krwi wiąże się z aż o 51% mniejszym ryzykiem rozwoju demencji i o 54% mniejszym ryzykiem choroby Alzheimera [00:01:30].
• Osoby szczególnie potrzebujące BDNF: Na podniesieniu poziomu BDNF mogą skorzystać osoby starsze, osoby po udarze mózgu (gdzie poziom spada o ok. 55%) [00:02:14], osoby z depresją [00:02:54], cukrzycą (w kontekście neuropatii) [00:03:30], żyjące w ciągłym stresie [00:05:12] oraz z nadwagą/otyłością [00:05:48].
• Czynniki obniżające BDNF: Negatywny wpływ na poziom BDNF ma przewlekły stres (poprzez kortyzol) [00:05:21] oraz alkohol (niezależnie od dawki) [00:06:33].
• Co podnosi BDNF (Dieta i Suplementacja):
  • Ser pleśniowy (np. Brie, Camembert, 30 g dziennie) [00:07:35].
  • Produkty bogate w kwas alfa-linolenowy (olej lniany, nasiona lnu, orzechy włoskie, nasiona chia) [00:08:00].
  • Kwasy tłuszczowe Omega-3 (tłuste ryby: łosoś, śledź, sardynki, makrela) [00:08:34].
  • Kurkumina (powyżej 500 mg dziennie) [00:08:50].
  • Cynk (30 mg glukonianu cynku dziennie lub z pożywienia: mięso, ryby, podroby, pestki dyni) [00:09:42]–[00:10:06].
  • Probiotyki (mieszanka szczepów Lactobacillus i Bifidobacterium) [00:10:25].
  • Dieta ketogeniczna (w badaniu po 3 tygodniach poziom BDNF był wyższy o 47%) [00:11:12].
  • Borówki, kakao i gorzka czekolada (badania na zwierzętach) [00:11:46].
• Co podnosi BDNF (Aktywność):
  • Ruch i ćwiczenia fizyczne (spacery, bieganie, siłownia, 3-4 razy w tygodniu, łącznie min. 2,5 godz. tygodniowo) [00:11:54]–[00:12:21].

Summary: - Finnish research links 4+ dry sauna sessions per week to a 40% reduction in all-cause mortality—this outpaces even regular exercise or a Mediterranean diet. - Bryan Johnson’s 90-day experiment: 20-minute dry sauna sessions at 200°F (93°C), up to 7 times weekly, following protocols based on Finnish studies. - Initial issues included severe muscle cramps and poor sleep, traced to dehydration and electrolyte loss from sweating; resolved by increasing electrolyte consumption before and after each session. - Cardiovascular benefits included a rapid reduction of central systolic blood pressure and improved arterial flexibility, due to heat-induced vasodilation. - Body detoxification: After multiple sessions, significant reductions in body toxin levels were observed, especially when showering after each sauna. - Fertility markers: Using an ice pack on the testes during sauna preserved and even improved fertility by 31% over 21 days; discontinuing ice resulted in a 50% drop in fertility markers, highlighting the importance of testicular cooling for men during regular sauna use. - Most studied health benefits are linked to dry saunas at high heat, rather than infrared or steam saunas. - Other improvements included lowered resting heart rate, healthier arteries (biologically ~10 years younger), and increased VEF (a growth signal for blood vessels and organ health). - Protocol recommendations: 3–5 dry sauna sessions per week, 15–20 minutes at 175–200°F (80–93°C); drink electrolytes, wear natural fibers, ice for male fertility, and shower promptly afterward. - Best stacked with exercise for additive benefits; if sauna isn’t available, vigorous exercise also induces similar cardiovascular adaptations. - Safety tips: Gradually work up to higher temperatures, stay hydrated, and avoid sauna if pregnant or with certain health conditions. - Fertility markers were restorable—“icing the boys” reversed the heat-related decline when restarted. - Conclusion: When combined with proper hydration, electrolyte replacement, and safety strategies (especially for male fertility), sauna is highly beneficial for cardiovascular health, detoxification, and overall recovery.

Results: - arteliar flexibility: +25-50% - vascular de-aging effect: ≈ 10 years younger - vascular age equivalent: ≈ 20-year-old level

Sauna Checklist: - Frequency: 3-5 sessions per week - Duration: 15-20 min per session - Temperature: 80-93°C - Type: dry sauna - After exercise: stronger effects - Stay hydrated with sufficient electrolytes - Coll the boys 🥚🥚 with non-toxic, BPA-free ice packs - To avoid toxins, wear cotton, bamboo, naked. Avoid synthetic fabrics - Don't put water on the rocks to avoid toxins getting into the air - After sauna do shower to wash off the toxins - If you don't have access to sauna, exercise as it also increases the body heat

• Eating timing matters: Stop eating at least 3 hours (ideally 10) before bed to boost HRV; late eating harms recovery.
• Diet quality: Higher HRV is associated with diets high in fish, vegetables, and fruit, and avoiding processed foods, seed oils, and high sodium.
• Consistency over specific diet types is key; less processed food and fewer calories help HRV (unless you're a performance athlete).
• Aerobic, endurance, and high-intensity interval training all increase HRV, with aerobic exercise having the most effect.
• Endurance training improves baroreceptor control and vagal tone; 1-2 sessions weekly recommended.
• High-intensity intervals (above 90% max HR) boost parasympathetic activity and HR recovery; occasional sessions are best.
• Weightlifting contributes less to HRV, but mixing it with more aerobic and interval work is optimal.
• Sleep greatly impacts HRV: Consistent bedtime, getting morning sunlight, daytime exercise, and avoiding late meals all help.
• Wind down 30 minutes before sleep; use breathing techniques like "box breathing" to relax and fall asleep quicker.
• Optimize sleep environment: Cool room (67°F), blackout curtains, calming music, mouth tape for nasal breathing.
• Sauna use increases plasma volume and can help HRV, as does cold exposure (cold showers/plunges) by providing hormetic stress.
• Devices (e.g., Petto for vagus nerve stimulation) may help but some like Sensate may be placebo.
• Reducing stress is crucial—doing meaningful work, fulfilling relationships, and low chronic stress (example: Warren Buffett).
• Combining diet, exercise, great sleep, minimal stress, and some environmental exposures (sauna/cold) is the best strategy for sustainably higher HRV.

General summary

• Obowiązek KSeF: Krajowy System e-Faktur (KSeF) wchodzi w życie 1 lutego 2024 roku. Należy już teraz nadawać uprawnienia dostępu.
• Moduł Certyfikatów i Uprawnień (MCU): Jest to tymczasowe rozwiązanie do zarządzania uprawnieniami. Docelowo funkcjonalność trafi do aplikacji podatnika KSeF 2.0.
• Metody Uwierzytelniania (Logowania) w KSeF:
  • Profil Zaufany (najczęściej stosowany).
  • Podpis kwalifikowany.
  • Pieczęć elektroniczna.
  • Certyfikat KSeF (najwygodniejszy w pracy z systemami księgowymi).
• Identyfikator w KSeF: Najważniejszym adresem, gwarantującym dostarczenie faktury, jest numer NIP.
• Uprawnienia Podstawowe: Można nadawać uprawnienia do wystawiania faktur, przeglądania faktur (kosztowych i przychodowych), przeglądania uprawnień (do nadawania/odbierania dalszych uprawnień) oraz przeglądania historii sesji.
• Nadawanie Uprawnień dla Podmiotów Innych niż JDG (Spółki, Spółki Cywilne): Wymagane jest złożenie papierowego lub elektronicznego druku ZAF-FA (Zgłoszenie/aktualizacja/odwołanie administratora) w celu wyznaczenia pierwszej osoby (administratora) w systemie. Alternatywą jest Pieczęć Elektroniczna.
• Uprawnienia dla Biura Rachunkowego: Przedsiębiorca może nadać uprawnienia konkretnemu podmiotowi (biuru rachunkowemu) z prawem do dalszego przekazywania uprawnień, co pozwala biuru na przydzielenie dostępu do klientów swoim pracownikom.
• Certyfikaty KSeF: Są to dwuletnie "dowody tożsamości", które pozwalają na wygodne uwierzytelnianie się w KSeF (np. przez systemy księgowe bez każdorazowego logowania Profilem Zaufanym).
• Ilość Certyfikatów: Można wygenerować dwa certyfikaty: jeden do uwierzytelniania w systemie, drugi do wystawiania faktur w trybie offline.
• Generowanie Certyfikatu Podmiotu: Aby uzyskać certyfikat na spółkę (a nie na osobę fizyczną-administratora), konieczne jest posiadanie Pieczęci Elektronicznej do pierwszego uwierzytelnienia.
• Certyfikat dla Księgowego: Księgowy korzysta z własnego certyfikatu (jako osoba fizyczna), który w połączeniu z nadanymi mu przez klienta uprawnieniami pozwala na dostęp do faktur klienta.
• Faktury Zagraniczne: Faktury przychodowe dla kontrahentów zagranicznych (z NIP UE lub spoza UE) muszą być wystawiane w KSeF. Faktury kosztowe otrzymane od kontrahentów zagranicznych nie będą trafiać do KSeF.

JDG summary

📝 KSeF dla JDG (Profil IT): Kluczowe Informacje

• Łatwość Dostępu dla JDG: Jako osoba fizyczna prowadząca JDG, masz automatyczny, pełny dostęp do KSeF (przy użyciu Profilu Zaufanego lub podpisu kwalifikowanego) bez konieczności składania formularza ZAF-FA czy innych formalności wstępnych.
• Zarządzanie Uprawnieniami: Możesz samodzielnie i szybko nadawać uprawnienia innym osobom (np. księgowemu) bezpośrednio w systemie.
• Automatyzacja (Certyfikaty KSeF): Kluczowe dla branży IT jest wykorzystanie Certyfikatów KSeF. Pełnią one funkcję tokenów służących do uwierzytelniania maszynowego (np. dla Twojego programu księgowego lub systemów, które zintegrujesz z KSeF). Certyfikaty są ważne 2 lata.
• Dwa Certyfikaty: Możesz wygenerować dwa różne Certyfikaty KSeF: jeden do głównego uwierzytelniania, drugi dedykowany do generowania faktur w trybie offline (z kodem QR).
• Fakturowanie Offline: Wystawienie faktury poza KSeF (offline) wymaga użycia certyfikatu KSeF i musi nastąpić wysyłka do KSeF najpóźniej następnego dnia roboczego.
• Usługi Zagraniczne (Przychody): Faktury za usługi IT świadczone na rzecz kontrahentów zagranicznych (zarówno unijnych, jak i spoza UE) muszą być wystawiane w KSeF.
• Koszty Zagraniczne: Faktury kosztowe, które otrzymujesz od zagranicznych dostawców (np. subskrypcje, sprzęt), nie są przesyłane do KSeF.

Możesz już zacząć testować: https://pomoc.infakt.pl/hc/pl/articles/14972316754834-Integracja-z-KSeF-za-pomoc%C4%85-tokenu

Brief summary

Authress avoided downtime during the AWS us-east-1 outage by implementing a multi-region, redundant infrastructure with automated DNS failover using custom health checks, edge-optimized routing, and robust anomaly detection, backed by rigorous testing and incremental deployments to minimize risk and impact. Their system design assumes failure is inevitable and focuses on quick detection, seamless failover, and minimizing single points of failure through automation and continuous validation.

Long summary

• Authress experienced a major AWS us-east-1 outage affecting DynamoDB and other critical AWS services.
• They run infrastructure in us-east-1 due to customer location demands, despite known risks.
• AWS services like CloudFront, Certificate Manager, Lambda@Edge, and IAM control planes are centralized in us-east-1, impacting availability during incidents.
• Aiming for a 5-nines SLA (99.999% uptime) requires more than relying on AWS SLAs alone, which are insufficient.
• Simple single-region architectures fail to meet high reliability due to frequent AWS incidents.
• Authress recognizes "everything fails all the time" and designs systems assuming failure.
• Retry strategies are mathematically analyzed; third-party components must have at least 99.7% reliability to be usable.
• Multi-region redundant infrastructure with DNS failover via AWS Route 53 health checks enables automatic failover.
• Custom health checks validate actual service health beyond default DNS checks.
• Edge-optimized architecture using CloudFront and Lambda@Edge improves latency and provides better failover options.
• DynamoDB Global Tables replicate data across regions to support failover.
• Rigorous testing and validation, including application-level tests, mitigate risks of bugs in production.
• Incremental deployment (customer buckets) limits impact by rolling out changes gradually.
• Asynchronous validation tests check consistency across databases after deployments.
• Anomaly detection is used to identify meaningful incidents impacting business logic, beyond mere HTTP error codes.
• Customer support feedback is integrated into incident detection to catch undetected or gray failures.
• Security measures include rate limiting, AWS WAF with IP reputation lists, and blocking suspicious high-volume requests.
• Resource exhaustion prevention is critical, with rate limiting implemented at multiple infrastructure layers.
• Infrastructure as Code (IaC) deployment differences across regions and edge leads to challenges in consistency.
• Despite all these measures, achieving a true 5-nines SLA is extremely challenging but remains a core commitment.

Summary of HN discussion

https://news.ycombinator.com/item?id=45955565

• The discussion highlights concerns about automation and Infrastructure as Code (IaC) being potential failure points, emphasizing the challenge of safely updating these systems.
• Rollbacks are rarely automatic; often, knowing in advance to avoid certain rollouts is preferable as automated rollbacks can worsen failures.
• Simple, less complex infrastructure changes are preferred to reduce human error, which is the leading cause of incidents.
• There is skepticism about the reliability of Route 53 failover in practice, with concerns about its failure modes and the complexity of multi-cloud DNS failover.
• Some contributors suggest modular IaC approaches (Pulumi, Terragrunt) for safer, repeatable deployments but warn about added complexity.
• Retry logic in failures is criticized; retries may not improve reliability linearly due to correlated failures and overall system overload during outages.
• Latency and client timeout constraints limit the practical number of retries possible.
• DNS is acknowledged as a single point of failure with caching and failover timing challenges.
• Multi-cloud failover at DNS level is complex, costly, and not widely implemented due to infrastructure and coordination requirements.
• Gray failures (where the system reports healthy but customers experience issues) and the difficulty in knowing real incident impact without customer feedback are noted.
• Customer support is critical in incident detection since automated systems cannot catch every failure.
• Detailed monitoring via CloudFront and telemetry helps identify actual service issues during outages.
• Overall, the theme is the difficulty in achieving perfect reliability, the importance of simplicity, and the need for layered detection and response strategies to manage failures.

• Author initially struggled with social skills, feeling awkward, excitable, and bullied due to abrasive behavior and sensitivity.

• Six stages of social learning show a progression from self-focused to deeply embodied connection strategies.

• Stage 1: Tried to be a dazzling, interesting, intellectual person to gain approval.

  • Emulated admired cultural figures, memorized poetry, and read complex literature.
  • Told dramatic personal stories and developed scholarly opinions.
  • This approach earned polarized approval, often distancing others because of its presentational quality.

• Stage 2: Learned to play the social game by adapting to others' social styles, especially in restaurant work.

  • Observed and mimicked the social behaviors that successful servers used.
  • Adopted flexible social roles matching the table's mood (efficient, flirtatious, etc.).
  • Made people feel comfortable by playing their "game," though still somewhat role-driven.

• Stage 3: Loosened grip on social scripts; used quirky, authentic behaviors to relax social interactions.

  • Added benign strangeness and surreal quirkiness to interactions to signal social playfulness.
  • Created moments of unexpected connection by breaking scripts sideways.
  • Learned that how things are said can be more important than what is said.

• Stage 4: Developed bodily awareness and real-time non-verbal communication like dancing with others.

  • Became attuned to subtle body language and unspoken emotional states.
  • Reacted fluidly and spontaneously to ongoing social and emotional cues.
  • This stage deepened presence beyond verbal skill to sensory social attunement.

• Stage 5: Practiced projecting love and acceptance, creating emotional openness and deep connection.

  • Embraced a meditative state of spacious openness inspired by energy healing.
  • Provided a nervous system capacity for emotional distress, enabling catharsis.
  • Found that deep listening and presence facilitated rapid emotional intimacy.

• Stage 6: Learned to moderate emotional connection, balancing openness with boundaries.

  • Recognized that constant emotional openness can be draining and misinterpreted.
  • Managed energetic boundaries and adjusted connection intensity according to context.
  • Balanced desire for connection with comfort in solitude and acceptance of varied social interaction levels.

• Author reflects on effects of spiritual openness in various social roles and the challenge of maintaining boundaries.

• Final insight: Genuine social connection evolves from crafted performance to embodied presence, balancing authenticity, empathy, and emotional limits.

• Media circulated a claim that Polish language is best for prompting, but this was not a conclusion from the OneRuler study.
• OneRuler is a multilingual benchmark testing how well language models process very long texts in 26 languages.
• Models performed on average best with Polish, but differences compared to English were small and not explained.
• Polish media prematurely concluded Polish is best for prompting, which the study's authors did not claim or investigate.
• The benchmark tested models on finding specific sentences in long texts, akin to CTRL+F, a function AI models inherently lack.
• Another task involved listing the most frequent words in a book; models often failed when asked to acknowledge if an answer was not present.
• Performance dropped likely because the task required full context understanding, not just text searching.
• Different books were used per language (e.g. Polish used "Noce i dnie," English used "Little Women"), impacting the fairness of comparisons.
• The choice of books was based on expired copyrights, which influenced the results.
• There is no conclusive evidence from this benchmark that Polish is superior for prompting due to multiple influencing factors.
• No model achieved 100% accuracy, serving as a caution about language models' limitations; outputs should be verified.
• Researchers advise caution especially when using language models for sensitive or private documents.
• The OneRuler study was reviewed and presented at the CoLM 2025 conference.

• Users appreciate Grafana's rich features but criticize its complexity and brittleness.
• Tools like Prometheus and Grafana are seen as over-engineered, especially with components like Mimir requiring dedicated infrastructure.
• Concerns exist about the future of self-hosted Grafana due to frequent breaking changes.
• Some suggest simpler, stable alternatives for monitoring such as Prometheus alone, Zabbix, VictoriaMetrics, or newer tools like SigNoz, OpenObserve, and Perses.
• The community desires a stable, reliable "boring" monitoring stack rather than constant feature churn.

Overall, there is notable dissatisfaction with Grafana’s direction and operational demands, particularly among smaller teams or startups seeking sustainable solutions.

• Henrik Gerdes warns that Grafana, despite being powerful, has become maintenance-heavy and complex, especially due to recent additions like Mimir and Kubernetes dependence.
• Stability issues, frequent breaking changes, and high operational overhead make it challenging for startups and teams needing reliable monitoring.
• Founders should consider total ownership costs, including updates, migrations, and support, before adopting Grafana.
• Grafana’s flexibility and scalability come with complexity that can erode trust in production environments.

• Jawność wynagrodzeń (od 24 grudnia 2025 r.)

  • Obowiązek ujawniania wynagrodzenia lub widełek płacowych przed rozmową kwalifikacyjną.
  • Zakaz pytania o wcześniejsze zarobki kandydata.
  • Oferty pracy muszą mieć neutralne płciowo nazwy stanowisk.
  • Wynagrodzenie obejmuje wszystkie składniki – premie, dodatki, benefity.
  • Od czerwca 2026 r. firmy zatrudniające ≥100 osób będą musiały raportować lukę płacową.
  • Wymagana aktualizacja polityki wynagrodzeń i szkoleń rekruterów.

• Nowe zasady liczenia stażu pracy (od 2026 r.)

  • Do stażu pracy będą wliczane umowy B2B, zlecenia i agencyjne objęte składkami ZUS.
  • Możliwość wydłużenia urlopu, odpraw i okresów wypowiedzenia.
  • Pracownik ma 24 miesiące na udokumentowanie wcześniejszej współpracy.
  • Firmy powinny przeanalizować historię zatrudnienia i zaktualizować regulaminy.
  • Zmiana zwiększy koszty organizacyjne i kadrowe.

• Nowe uprawnienia Państwowej Inspekcji Pracy (od 1 stycznia 2026 r.)

  • PIP będzie mógł samodzielnie stwierdzić istnienie stosunku pracy.
  • Decyzja administracyjna zastąpi wyrok sądu i będzie natychmiast wykonalna.
  • Możliwość zdalnych kontroli, żądania transmisji wideo, przesłuchań online.
  • Firmy muszą przeanalizować umowy cywilnoprawne pod kątem ryzyka uznania za etat.

• Mobbing i dyskryminacja – nowe przepisy

  • Zniesienie wymogu „długotrwałości” mobbingu – wystarczy uporczywe nękanie.
  • Minimalne zadośćuczynienie: 12-krotność miesięcznego wynagrodzenia.
  • Obowiązek wprowadzenia formalnej procedury antymobbingowej.
  • Nowe formy dyskryminacji: przez asocjację i przez domniemanie.
  • Wymagane szkolenia dla kadry i jasne procedury zgłaszania naruszeń.

• Cyfrowa komunikacja z pracownikami

  • Zastąpienie „formy pisemnej” przez „postać papierową lub elektroniczną”.
  • Możliwość komunikacji e-mail, przez komunikatory lub SMS.
  • Pracodawca musi udowodnić doręczenie wiadomości.
  • Konieczność aktualizacji regulaminu pracy i zgodności z RODO.

• Płaca minimalna 2026

  • Od 1 stycznia 2026 r. wzrost do 4806 zł brutto/miesiąc i 31,40 zł brutto/godz.
  • Wzrost kosztów zatrudnienia, składek ZUS i świadczeń.
  • Firmy powinny uwzględnić zmiany w budżetach kadrowych.

• Polityka AI w organizacji

  • Wymóg wprowadzenia zasad korzystania z AI zgodnie z unijnym AI Act.
  • Brak polityki może zostać uznany za naruszenie obowiązków pracodawcy.
  • Konieczność określenia, gdzie AI można, a gdzie nie można stosować.

• Podsumowanie działań dla firm

  • Zaktualizować regulaminy i umowy.
  • Przeszkolić menedżerów i dział HR.
  • Przygotować system do raportowania płac i cyfrowego obiegu dokumentów.
  • Przeanalizować umowy B2B i zlecenia pod kątem ryzyka PIP.
  • Wczesne przygotowanie zapewni spokój i przewagę konkurencyjną.

On why documentation is important

• AWS EKS costs can escalate due to massive, parallel workloads in life sciences/drug development (e.g., genomic sequencing, molecular modeling).
• Default Kubernetes scheduler uses leastAllocated strategy, spreading pods across many nodes for fairness/high availability.
• leastAllocated strategy causes many partially utilized nodes, preventing autoscalers from scaling down idle nodes, increasing costs.
• mostAllocated scheduling strategy "packs" pods onto fewer nodes, maximizing utilization and enabling autoscalers like Karpenter to remove idle nodes.
• Switching to mostAllocated can reduce runtime costs significantly (e.g., ~10% in UAT, 43% in PROD environments).
• Custom scheduler deployment on AWS EKS requires creating a service account, ClusterRoleBindings, RoleBinding, a ConfigMap with the mostAllocated scoring strategy, and a deployment with a matching Kubernetes version container image.
• Resource weights can prioritize packing of expensive resources (e.g., high weight on GPUs for ML workloads).
• Testing in non-production environments is recommended before full rollout.
• Implementing mostAllocated scheduling can dramatically optimize costs by enabling cluster autoscalers to shut down unused nodes.

From this discussion, it’s clear that using Allegro Pay isn’t inherently bad, but it can be disadvantageous in certain situations — especially if you plan to apply for a mortgage or larger bank loan soon. Here are the key takeaways:

🟢 When using Allegro Pay is fine

• If you repay everything on time (e.g., within 30 days) and don’t have many active purchases at once.
• If you use it occasionally, for example to avoid freezing your cash or to grab a promotion (like a 30 PLN coupon).
• If you’re not planning any major loans soon, small transactions usually don’t make much difference.

🔴 When you should AVOID Allegro Pay

• If you plan to take out a mortgage or consumer loan within the next few months – banks see these purchases in your credit report (BIK) as short-term loans (BNPL), sometimes even classified as payday loans.
• Each purchase can appear as a separate entry in your BIK, so frequent usage might look like a large number of small loans, which can lower your credit score and borrowing capacity.
• Some banks (e.g., BNP Paribas, Pekao, Millennium – according to users’ reports) have automated systems that reduce creditworthiness if multiple BNPL loans are active.

⚖️ Summary

• For a one-time promotion (e.g., 30 PLN coupon) – it’s okay to use, but repay immediately after the purchase.
• Avoid regular use if you’re planning a mortgage or major loan within the next 12–24 months.
• Allegro Pay is visible in BIK, so even small transactions leave a footprint in your credit history.

👉 Conclusion: If you want to maintain a spotless credit profile — avoid Allegro Pay. If you’re not planning any big loans — occasional use is perfectly fine, as long as you repay on time

Summary of the HN discussion:

• Happiness sources like relationships, satisfying work, and accomplishment do not strongly depend on intelligence, and intelligence does not guarantee better outcomes in these areas.
• Smart people tend to see more variables and possible changes in life, leading to higher expectations and sometimes less contentment.
• Happiness is influenced more by emotional intelligence, perspective, acceptance, and social connection than by raw IQ.
• Many participants emphasized that happiness is complex, often fleeting, and influenced by factors beyond intelligence such as disposition, environment, and life experience.
• Some noted that smart people can overthink or struggle with executing actions, resulting in paralysis or dissatisfaction despite knowledge.
• Wisdom, virtue, and the ability to align actions with true desires are viewed as more crucial for happiness than intelligence alone.
• There is skepticism about equating intelligence with rationality; highly intelligent people may still struggle with irrational beliefs or poor social skills.
• Social belonging and meaningful human interactions are highlighted as critical for well-being, sometimes more than intellectual capability.
• Discussions touched on the limitations of happiness measures and the idea that intelligence may increase awareness of life's challenges, contributing to lower subjective happiness in some cases.
• The notion of happiness as a fixed or baseline state shaped by evolution was also mentioned, suggesting intelligence alone does not alter this baseline.

Summary below (also check HN discussion):

• Intelligence, defined as general mental ability, surprisingly shows little to no strong positive correlation with personal happiness. Sometimes the correlation is even slightly negative.
• IQ tests mainly measure skill at solving well-defined problems with clear rules and solutions, not the ambiguous, complex, poorly defined problems of life that shape long-term happiness.
• Life’s poorly defined problems (e.g., "how to live a good life") require wisdom, creativity, and self-knowledge, which are not captured by IQ tests.
• Extremely intelligent people can still struggle with basic life challenges and moral decisions despite high IQ scores.
• Studies show lower IQ groups sometimes report less happiness, but factors like health, income, and social support strongly mediate that relationship.
• Happiness is influenced by emotional intelligence and social circumstances as much or more than raw IQ.
• AI excels at well-defined problem solving but is incapable of addressing poorly defined, human-centric questions related to happiness and meaning.
• The gap between intelligence and happiness highlights the need to value wisdom and human judgment beyond testable intelligence.
• The ability to choose meaningful goals and persist with them (called "directionness") may be a key factor in life satisfaction, separate from IQ.

• AI, intended to free workers, is causing longer work hours and increased pressure, spreading 996 culture to Western AI startups.
• AI tools never tire, creating psychological pressure to constantly work and increasing feelings of guilt during rest.
• Historical advances like lamps and bulbs extended work hours; AI similarly shifts "can work" into "should work."
• Philosopher Byung-Chul Han's "Burnout Society" concept shows internalized self-discipline drives overwork, amplified by AI's "excess of positivity."
• The hyper-productivity loop leads to burnout, reduced creativity, and diminishing returns despite increased effort.
• Rest is framed as resistance and vital for innovation, which thrives on reflection, not constant activity.
• The key challenge is adopting a healthy culture around AI use that avoids exploitation and preserves human well-being.

5 general rules for good reviews

Rather leave one comment about subtle things, than multiple ones

Tips on making effective code reviews (don't just focus on the diff)

• The iLife A11 smart vacuum was found to constantly send detailed data, including 3D home maps, to manufacturer servers without explicit user consent.
• When the user blocked telemetry transmissions, the vacuum was remotely disabled by a command from the manufacturer, resulting in repeated failures.
• Reverse engineering revealed the device runs a Linux OS with an open root access port and includes software allowing the manufacturer to remotely control or disable it.
• Service centers temporarily restored functionality by reconnecting the device to manufacturer servers, but it failed again once telemetry was blocked.
• This hardware and practice are common in many smart vacuums from brands like Xiaomi, Wyze, and Viomi, raising broad privacy and control concerns.
• The case highlights significant security risks and loss of user autonomy inherent to many "smart" IoT devices relying on cloud connectivity.

• Running can counteract some negative effects of an unhealthy, Western-style diet, according to researchers from University College Cork.
• The study found that exercise restores key metabolites linked to mental well-being and balances crucial hormones disrupted by a diet high in sugar, fat, and processed foods.
• Rats fed high-calorie “cafeteria diet” foods showed major disturbances in gut metabolism, with 100 out of 175 metabolites significantly altered; running partially restored balance, especially for anserine, indole-3-carboxylate, and deoxyinosine.
• Physically active rats on the same poor diet had normalized levels of insulin and leptin compared to sedentary ones, showing exercise helps regulate hormonal balance.
• The body activated compensatory hormonal mechanisms, such as changes in GLP-1 and PYY levels, to stabilize metabolism under poor dietary conditions.
• The study also linked exercise to improved neurogenesis (formation of new neurons) in the hippocampus, but only when paired with a healthy diet—junk food appeared to suppress this regenerative effect.
• Despite running’s benefits, researchers emphasized that good nutrition remains essential for full brain health and mental performance.
• The findings offer insight into how exercise may protect mental well-being even amid widespread consumption of processed foods.

• Internal documents reviewed by The New York Times show Amazon plans to automate up to 75% of its operations in the coming years.
• The company expects automation to replace or eliminate over 500,000 U.S. jobs by 2033, primarily in warehouses and fulfillment centers.
• By 2027, automation could allow Amazon to avoid hiring around 160,000 new workers, saving about 30 cents per package shipped.
• This strategy is projected to save $12.6 billion in labor costs between 2025 and 2027.
• Amazon’s workforce tripled since 2018 to approximately 1.2 million U.S. employees, but automation is expected to stabilize or reduce future headcount despite rising sales.
• Executives presented to the board that automation could let the company double sales volume by 2033 without needing additional hires.
• Amazon’s Shreveport, Louisiana warehouse serves as the model for the future: it operates with 25% fewer workers and about 1,000 robots.
• A new facility in Virginia Beach and retrofitted older ones like Stone Mountain, Georgia, are following this design, which may shift employment toward more temporary and technical roles.
• The company is instructing staff to use softer language—such as “advanced technology” or “cobots” (collaborative robots)—instead of terms like “AI” or “robots,” to ease concerns about job loss.
• Amazon has begun planning community outreach initiatives (parades, local events) to offset the reputational risks of large-scale automation.
• The company has denied that the documents represent official policy, claiming they reflect the views of one internal group, and emphasized ongoing seasonal hiring (250,000 roles for holidays).
• Analysts suggest this plan could serve as a blueprint for other major employers, including Walmart and UPS, potentially reshaping U.S. blue‑collar job markets.
• The automation push continues a trajectory started with Amazon’s $775 million acquisition of Kiva Systems in 2012, which introduced mobile warehouse robots that revolutionized internal logistics.
• Recent innovations include robots like Blue Jay, Vulcan, and Proteus, aimed at performing tasks such as sorting, picking, and packaging with minimal human oversight.
• Long-term, Amazon may require fewer warehouse workers but more robot technicians and engineers, signaling a broader shift in labor type rather than total employment.

Plug-in hybrid vehicles (PHEVs) are not as environmentally friendly as previously claimed, according to recent EU data.

• Real-world emissions from PHEVs average 135 g CO₂/km, only 19% less than conventional petrol and diesel cars which average 166 g CO₂/km.
• Official WLTP tests significantly underestimate emissions; PHEVs often run on the combustion engine, even in electric mode, increasing real fuel consumption.
• In electric-only mode, PHEVs still burn around 3 liters of petrol per 100 km, resulting in emissions of 68 g CO₂/km—over eight times higher than manufacturers’ claims.
• Hidden fuel consumption costs drivers approximately 500 euros per year more than official manufacturer data suggests.
• PHEVs are among the most expensive on the market; average price in 2025 in Germany, France and the UK is 55,700 euros, about 15,000 euros higher than average battery-only electric cars.
• Increasing electric range through larger batteries does not reduce emissions; heavier vehicles consume more fuel and energy overall.
• PHEVs with electric ranges above 75 km emit more CO₂ on average than those with ranges of 45–75 km.
• The biggest discrepancies are noted for Mercedes-Benz plug-in hybrids; in 2023, their real emissions exceeded official figures by an average of 494%, with the GLE-Class over by 611%.
• Automotive industry is lobbying to have PHEVs recognized as low-emission beyond 2035, despite new EU regulations that require the transition to zero-emission vehicles.
• Weakening EU regulations could undermine the development and adoption of truly zero-emission technologies.
• According to Transport & Environment, plug-in hybrids are “one of the biggest myths in motoring,” often emitting almost as much as combustion-engine cars and much more than test results indicate.
• EEA and T&E data casts doubt on PHEVs as effective solutions for transportation decarbonization; their environmental benefits are increasingly questioned.

• The article describes the case of a user (Mateusz) whose Google account was hijacked after he ran malware (a stealer) sent from a compromised friend's Discord account.
• The malware stole the user's active session cookie, not their password. This allowed the attacker to bypass all login protections, including 2-Step Verification (like a YubiKey), because they were able to take over an already-authenticated session without needing to log in.
• Using this hijacked session, the attacker convinced Mateusz to join a "Family Group" (Google Family Link) and simultaneously changed his account's birth date to an age under 13.
• This action immediately flagged the account as a "child's account," with the attacker as the "parent/guardian," which locked Mateusz out and triggered a 14-day permanent deletion process.
• Mateusz is now in a "digital Catch-22": standard account recovery forms do not work for "child accounts," and Google's support (including YouTube and Google Play) has been unhelpful, closing his tickets despite him having proof of ownership.
• The article criticizes Google for an "astounding oversight" in its business logic that allows an adult account's age to be so easily changed to a child's, creating a major vulnerability.
• As a result, Mateusz lost 13 years of data (Gmail, Drive, Contacts) and access to all his purchases on Google Play.
• The article concludes that since 2FA can't stop session hijacking, the only effective way to protect against the data loss from this specific attack is to regularly back up your Google account data using Google Takeout.

Based on YT video I Ate 720 Eggs in 1 Month. Here's What Happened to my Cholesterol:

• Nick Norwitz, a Harvard medical student with a doctorate in human cerebral metabolism, ate 720 eggs in one month, averaging 24 eggs per day, to test the effects on his cholesterol levels.
• Contrary to popular belief that eggs increase bad cholesterol (LDL), his LDL cholesterol dropped during the experiment. It decreased by 2% in the first two weeks and then by an additional 18% in the next two weeks.
• The high cholesterol intake (about 133,000 mg from eggs) did not raise his blood cholesterol. This was explained by a hormone called cholesin, released when cholesterol binds to receptors in the gut, which signals the liver to reduce cholesterol production, maintaining balance in the body.
• During the last two weeks, he also increased carbohydrate intake slightly, which further helped reduce LDL levels, possibly in combination with other dietary elements like fruits.
• The experiment challenges the long-held medical advice limiting egg consumption due to cholesterol concerns, suggesting that dietary cholesterol may not significantly impact blood cholesterol levels in healthy individuals.
• Norwitz documented his experiment publicly on YouTube, sparking discussions on nutrition and metabolism and encouraging re-evaluation of egg consumption guidelines.
• Eggs are a veritable treasure trove of nutrients: harmful vitamins A, D, E, and K, harmful B vitamins, calcium, phosphorus, iron, sodium, and potassium. However, even such a valuable product should not replace other essential nutrients.

• The world's oldest verified person, Maria Branyas Morera, lived to 117 years and 168 days, surpassing the average lifespan by over 30 years.
• A comprehensive study analyzed her genetics, epigenetics, metabolism, immunity, and gut microbiome using blood, saliva, urine, and stool samples.
• Despite her advanced age, she exhibited excellent health: low inflammation, healthy lipid profile, protection against age-related illnesses, and no cancer or neurodegenerative diseases.
• Her biological age (measured by epigenetic markers) was much younger than her chronological age, suggesting her cells aged more slowly.
• No single “longevity gene” was found; instead, her longevity was linked to a rare combination of genetic variants, a robust immune system, a healthy Mediterranean diet, daily physical activity, and an exceptionally diverse gut microbiome rich in Bifidobacterium.
• Her lifestyle choices—never smoking or drinking alcohol, walking daily, and eating three yogurts a day—supported her gut health and helped keep inflammation low.
• Researchers emphasized that both genetic factors and environmental/lifestyle influences interplay, and that aspects like diet, stress reduction, and supporting a healthy microbiome may help slow biological aging.
• The study’s results suggest the importance of healthy aging (maintaining function and independence in old age), and reinforce the idea that everyone can potentially influence their rate of aging through lifestyle, even if they don’t carry rare longevity genes.

Video summary:

• Core idea: People default to one of four communication “colors” and connect best when adapting to the other person’s style.
• The four colors: Red (power/results), Green (peace/stability), Blue (logic/structure), Yellow (fun/connection).

• Framework origin: Model popularized by Thomas Erikson’s “Surrounded by Idiots,” mapping to DISC-like styles via colors.

• Identify own color with 3 questions: 1) introverted (blue/green) vs extroverted (red/yellow); 2) logical (blue/red) vs emotional (green/yellow); 3) deliberate (green/blue) vs fast speaker (yellow/red); combine answers to narrow to one color.

• Everyone is a mix, but most have a dominant default; conflicts arise when speaking only in one’s own color.

• Matching styles creates instant rapport; mismatch leads to misjudgments (e.g., reds seen as abrasive by others, blues as nitpicky).

• How others may perceive each color:

  • Red: pushy to greens, too serious to yellows, reckless with details to blues.
  • Yellow: unfocused to reds, chaotic to greens, superficial to blues.
  • Green: indecisive to reds, boring to yellows, non-committal to blues.
  • Blue: too slow for reds, overly critical for yellows, nitpicky for greens.

• How to talk to each color:

  • To Red: be direct, decisive, confident; use frameworks; focus on outcomes, not fluff.
  • To Yellow: be enthusiastic and story-driven; keep it light and fun; don’t drown them in manuals.
  • To Green: be calm, patient, supportive; move at a comfortable pace; avoid rushing change.
  • To Blue: be precise, structured, factual; bring data and step-by-step plans; avoid exaggeration.

• Practical tip: Keep the 3 self-check questions visible during calls to rapidly gauge color and adjust delivery.

• Mindset shift: Don’t “change who you are”; expand range to “speak all four languages” to connect with 95% of people.
• Personal example: Vinh (Yellow) adapted to spouse (Red) by cutting fluff, adding clarity and speed to avoid overwhelm.
• Goal: Become dynamic “like water,” meeting people where they are without losing identity; communication skill lifts every area of life.

MIT report: 95% of companies see no profit from investments in generative AI, which amounted to approximately $35 billion.

Most AI pilots have no measurable impact on company profits. Attempts to implement tools like ChatGPT into the workplace primarily increase the productivity of individual employees, not the earnings of the entire company.

• DRA goes mainstream: stable core with ResourceClaim/DeviceClass and structured parameters — finally flexible, sane GPU/accelerator management without node‑selector tricks or quota hacks.
• Ops bonuses: production‑ready kubelet/API Server tracing (end‑to‑end debugging), new Deployment pod replacement policies (faster vs. resource‑conservative), PreferSameNode/SameZone traffic distribution, KYAML output in kubectl, and per‑HPA configurable tolerance.
• Zero breaking changes: no deprecations or removals — smooth upgrade for production teams.
• Release planned for late August

lol

Summary: Navigating Failures in Pods With Devices

This article examines the unique challenges Kubernetes faces in managing specialized hardware (e.g., GPUs, accelerators) within AI/ML workloads, and explores current pain points, DIY solutions, and the future roadmap for more robust device failure handling.

Why AI/ML Workloads Are Different

• Heavy Dependence on Specialized Hardware: AI/ML jobs require devices like GPUs, with hardware failures causing significant disruptions.
• Complex Scheduling: Tasks may consume entire machines or need coordinated scheduling across nodes due to device interconnects.
• High Running Costs: Specialized nodes are expensive; idle time is wasteful.
• Non-Traditional Failure Models: Standard Kubernetes assumptions (like treating nodes as fungible, or pods as easily replaceable) don’t apply well; failures can trigger large-scale restarts or job aborts.

Major Failure Modes in Kubernetes With Devices

1. Kubernetes Infrastructure Failures

   • Multiple actors (device plugin, kubelet, scheduler) must work together; failures can occur at any stage.
   • Issues include pods failing admission, poor scheduling, or pods unable to run despite healthy hardware.
   • Best Practices: Early restarts, close monitoring, canary deployments, use of verified device plugins and drivers.

2. Device Failures

   • Kubernetes has limited built-in ability to handle device failures—unhealthy devices simply reduce the allocatable count.
   • Lacks correlation between device failure and pod/container failure.
   • DIY Solutions:
     • Node Health Controllers: Restart nodes if device capacity drops, but these can be slow and blunt.
     • Pod Failure Policies: Pods exit with special codes for device errors, but support is limited and mostly for batch jobs.
     • Custom Pod Watchers: Scripts or controllers watch pod/device status, forcibly delete pods attached to failed devices, prompting rescheduling.

3. Container Code Failures

   • Kubernetes can only restart containers or reschedule pods, with limited expressiveness about what counts as failure.
   • For large AI/ML jobs: Orchestration wrappers restart failed main executables, aiming to avoid expensive full job restart cycles.

4. Device Degradation

   • Not all device issues result in outright failure; degraded performance now occurs more frequently (e.g., one slow GPU dragging down training).
   • Detection and remediation are largely DIY; Kubernetes does not yet natively express "degraded" status.

Current Workarounds & Limitations

• Most device-failure strategies are manual or require high privileges.
• Workarounds are often fragile, costly, or disruptive.
• Kubernetes lacks standardized abstractions for device health and device importance at pod or cluster level.

Roadmap: What’s Next for Kubernetes

SIG Node and Kubernetes community are focusing on:

• Improving core reliability: Ensuring kubelet, device manager, and plugins handle failures gracefully.
• Making Failure Signals Visible: Initiatives like KEP 4680 aim to expose device health at pod status level.
• Integration With Pod Failure Policies: Plans to recognize device failures as first-class events for triggering recovery.
• Pod Descheduling: Enabling pods to be rescheduled off failed/unhealthy devices, even with restartPolicy: Always.
• Better Handling for Large-Scale AI/ML Workloads: More granular recovery, fast in-place restarts, state snapshotting.
• Device Degradation Signals: Early discussions on tracking performance degradation, but no mature standard yet.

Key Takeaway

Kubernetes remains the platform of choice for AI/ML, but device- and hardware-aware failure handling is still evolving. Most robust solutions are still "DIY," but community and upstream investment is underway to standardize and automate recovery and resilience for workloads depending on specialized hardware.

A Harvard Law graduate who argued before the Supreme Court fed his case briefs into Claude 4 Opus and had it answer the same questions the Justices posed to him. The AI delivered what he called an "outstanding oral argument" with coherent answers and clever responses he hadn't considered, leading him to conclude that AI lawyers could soon outperform even top human advocates at oral argument.

• Sauna use induces mild heat stress, activating natural repair processes in the body such as heat shock proteins, improved blood flow, antioxidant activity, metabolism optimization, reduced inflammation, and enhanced immunity, all contributing to whole-body health benefits.

• Regular sauna sessions (4–7 times/week, at least 19 minutes) are strongly associated with improved heart health, significantly lowering the risk of heart disease (by up to 48%) and high blood pressure (by up to 47%).

• Mental health benefits include better sleep (over 80% report improvement), reduced muscle pain, improved mood, and a lower risk of dementia (up to 48% reduction) and psychotic disorders (up to 77% reduction) with frequent use.

• Sauna use reduces systemic inflammation, with frequent sessions leading to up to 31.5% lower inflammation markers and easing symptoms of chronic inflammatory and autoimmune conditions like rheumatoid arthritis.

• Metabolic improvements include decreased bad cholesterol (LDL), transiently lower triglycerides, and small increases in good cholesterol (HDL); some studies show increased muscle mass and bone density after intensive sauna protocols.

• Saunas may aid detoxification by promoting sweat-induced elimination of heavy metals and environmental toxins, with longer sessions (15–20+ minutes) enhancing this effect.

• Frequent sauna use is linked to increased longevity, with studies showing up to 40% lower all-cause mortality and up to 70% lower risk of dying from heart disease for those using saunas 4–7 times per week.

• Bryan Johnson’s personal protocol involves daily 20-minute dry sauna sessions at 93°C (200°F), with hydration and protective measures, and he tracks various biomarkers to measure health impacts.

• Recommended sauna practice: 3–5 sessions per week, 15–20 minutes each at 80–90°C (175–194°F), ideally post-workout; always hydrate and avoid sauna use if dehydrated, unwell, or with certain medical conditions.

• Results from Bryan Johnson’s ongoing self-experimentation are forthcoming, but current evidence supports sauna as a promising intervention for detox, longevity, and overall health.

• NVIDIA’s latest earnings highlight a dramatic surge in AI demand, driven by a shift from simple one-shot inference to more complex, compute-intensive reasoning tasks.
• Reasoning models require hundreds to thousands of times more computational resources and tokens per task, significantly increasing GPU usage, especially for AI coding agents and advanced applications.
• Major hyperscalers like Microsoft, Google, and OpenAI are experiencing exponential growth in token generation, with Microsoft alone processing over 100 trillion tokens in Q1—a fivefold year-over-year increase.
• Hyperscalers are deploying nearly 1,000 NVL72 racks (72,000 Blackwell GPUs) per week, and NVIDIA-powered “AI factories” have doubled year-over-year to nearly 100, with the average GPU count per factory also doubling.
• To meet this unprecedented demand, more than $300 billion in capital expenditure is being invested this year in data centers (rebranded by NVIDIA as “AI factories”), signaling a new industrial revolution in AI infrastructure.

That's even too much for me.

• 🦶 10,000 steps a day is the minimum<br /> Regular physical activity, even in the form of a 15–30 minute walk daily, can extend life by 3–5 years. The exact number of steps doesn't matter—what counts is consistent movement.

• 🔁 Day of effort, day of rest<br /> Daily intense exercise, such as running 10 km, can lead to physiological stress. A recommended rhythm is one day of activity followed by one day of recovery, which supports the creation of new mitochondria.

• 🌬️ What happens during the break<br /> On the rest day, the body prepares for the next activity: it creates mitochondria, replenishes energy, and regenerates cellular structures.

• 🧠 Physical activity affects the brain and hormones<br /> Movement reduces cortisol, which increases levels of testosterone and estrogen. This influences libido and overall mood.

• 💧 Hydration is essential<br /> Activity increases water loss—you should drink at least 1.5–2.5 liters of water daily. Avoid dehydration caused by coffee, alcohol, and tea.

• 🌲 Best activity is outdoors<br /> Walking in the forest is more beneficial than exercising in the city—better microbiota, fewer toxins, and cleaner air.

📊 Insights Based on Numbers

• 🚶‍♀️ 15-minute walk daily = +3 years of life
• 🏃‍♂️ 30 minutes daily = +5 years of life
• 💧 Body loses about 2.5 liters of water daily through sweat, breath, and urine
• 🏃‍♂️ 4 km walk to and from work = full daily dose of activity

• Average BMI in Poland: The average BMI of Poles is 26.33, which falls into the overweight category (BMI ≥ 25). Approximately 60% of Poles are classified as overweight.
• Comparison with Hungary: Poland and Hungary have the highest proportion of overweight individuals in Europe.
• Physical Activity in Poland:
  • Poland ranks second to last in Europe regarding physical activity levels.
  • Over one-third of Poles hardly engage in sports.
  • The average number of weekly physical activities has dropped from 3 to 2.7, the second-lowest in Europe (Hungary ranks lowest at 2.4).
• BMI Trends in Europe: In the past decade, BMI has increased across most European countries.
• Countries with the Fewest Overweight Issues: Switzerland, Austria, France, and Italy have the lowest prevalence of overweight individuals.

• Revolut accounts are difficult for Polish bailiffs to seize because the bank operates under a Lithuanian license and does not have a branch or headquarters in Poland. It is not part of the OGNIVO system, which facilitates communication between banks and enforcement authorities.

• Revolut operates legally in Poland through cross-border services under the "single passport" rule. Deposits are protected up to €100,000 by the Bank of Lithuania, ensuring client security.

• Polish IBANs are available through Revolut via cooperation with Aion Bank, enabling users to receive salaries, make transfers, and use payment systems like BLIK.

Sounds like it's better to look for Bosch engines than Shimano in e-bikes

See the summary below this highlight

• Introduction

  • Containers are widely used for scalable applications but face challenges with startup times for large images (e.g., AI/ML workloads).
  • Pulling large images from Amazon Elastic Container Registry (ECR) can take several minutes, impacting performance.
  • Bottlerocket, an AWS open-source Linux OS optimized for containers, offers a solution to reduce container startup time.

• Solution Overview

  • Bottlerocket's data volume feature allows prefetching container images locally, eliminating the need for downloading during startup.
  • Prefetching is achieved by creating an Amazon Elastic Block Store (EBS) snapshot of Bottlerocket's data volume and mapping it to new Amazon EKS nodes.
  • Steps to implement:
  • Spin up an Amazon EC2 instance with Bottlerocket AMI.
  • Pull application images from the repository.
  • Create an EBS snapshot of the data volume.
  • Map the snapshot to Amazon EKS node groups.

• Benefits of Bottlerocket

  • It separates OS and container data volumes, ensuring consistency and security during updates.
  • Prefetched images significantly reduce startup times for large containers.

• Implementation Walkthrough

  • Step 1: Build EBS Snapshot
    • Automate snapshot creation using a script.
    • Prefetch images like Jupyter-PyTorch and Kubernetes pause containers.
    • Export the snapshot ID for use in node group configuration.
  • Step 2: Setup Amazon EKS Cluster
    • Create two node groups:
    • no-prefetch-mng: Without prefetched images.
    • prefetch-mng: With prefetched images mapped via EBS snapshot.
  • Step 3: Deploy Pods
    • Test deployment on both node groups.
    • Prefetched nodes start pods in just 3 seconds, compared to 49 seconds without prefetching.

• Results

  • Prefetching reduced container startup time from 49 seconds to 3 seconds, improving efficiency and user experience.

• Further Enhancements

  • Use Karpenter for automated scaling with Bottlerocket nodes.
  • Automate snapshot creation in CI pipelines using GitHub Actions.

• Cleaning Up

  • Delete AWS resources (EKS cluster, Cloud9 environment, EBS snapshots) to avoid charges after testing.

• Conclusion

  • Bottlerocket's data volume prefetching dramatically enhances container startup performance for large workloads on Amazon EKS.

• Net Profit:

  • In 2024, Orlen's net profit amounted to 7.95 billion PLN, compared to 20.97 billion PLN in 2023.

• Sales Revenue:

  • Dropped to 296.95 billion PLN in 2024 from 372.77 billion PLN in 2023.

• Dividend:

  • The board recommends a dividend payout of 6 PLN per share for 2024, an increase from 4.15 PLN per share in 2023.
  • The total amount allocated for dividends is 6.966 billion PLN.

• Business Segments:

  • Refining: Revenue decreased by 16.89 billion PLN (5% year-over-year), mainly due to lower gasoline (-9%), diesel (-10%), jet fuel (-10%), and light heating oil (-9%) prices.
  • Energy: Revenue fell by 10.04 billion PLN, impacted by a 12% drop in sales volume to 28.5 TWh and a 19% lower electricity price on the Polish Power Exchange.
  • Petrochemicals: Revenue increased by 760 million PLN due to a 9% growth in sales volume to 4.788 million tons and higher prices for key products such as ethylene (+1%), benzene (+11%), polyethylene (+5%), and polypropylene (+3%).
  • Retail: Revenue rose by 4.65 billion PLN as fuel sales volume increased by 11% to 11.308 million tons.
  • Upstream (Oil & Gas Production): Revenue grew by 882 million PLN due to a 23% increase in sales volume, driven by higher hydrocarbon production and the consolidation of the KUFPEC Norway AS acquisition.

• Overall Takeaway:

  • Despite a significant decline in net profit and revenue, Orlen plans to distribute a record dividend, reflecting its strategy of sharing profits with shareholders.

Claude 3.7 Sonnet again excels at coding, as verified by multiple teams

About Claude 3.7 Sonnet

• Why use Kubernetes

  • Best for running multiple processes/servers/jobs with redundancy and load balancing
  • Enables infrastructure-as-code configuration for service relationships
  • Outsourced infrastructure management via cloud providers (e.g., Google Kubernetes Engine)

• What they use

  • Core resources: Deployments (with rolling updates), Services (ClusterIP/LoadBalancer), CronJobs
  • Configuration: ConfigMaps and Secrets via Pulumi (TypeScript) instead of raw YAML
  • Cautious adoptions: StatefulSets for limited persistence, RBAC only when necessary

• What they avoid

  • Hand-written YAML and Helm charts ("fragility for no gain")
  • Operators, custom resources, service meshes, and most third-party controllers
  • Local k8s stack replication (prefer Docker Compose for local dev)

• Key insights

  • "A human should never wait for a pod" - unsuitable for interactive workloads requiring fast startup
  • Use managed databases/storage for critical data instead of k8s volumes
  • Alternatives like Railway/Render may be better for simpler SaaS apps
  • Recently adopted Ingress controllers for Cloud Armor integration despite initial reservations

Chinese cars with record sales growth in Poland, in January 1000% increase in registrations year-on-year (2 thousand), and their market share jumped to 5%; the most popular brand is MG (1 thousand units), ahead of e.g. Fiat, Citroën, Suzuki and Opel.

In the whole of 2024, 11 thousand Chinese cars were registered, and in 2023 only 160.

Prices of the cheapest Chinese cars:

• MG3 PLN 73.5 thousand, 1.5 l engine
• BAIC Beijing 3: PLN 79 thousand, 1.5 l engine
• MG ZS Classic PLN 80 thousand, 1.5 l engine

The cheapest hybrid: MG ZS Hybrid+: PLN 99 thousand, 1.5 l engine.

• Daily intake of 1g of omega-3 fatty acids can slow down aging, especially when combined with vitamin D and exercise - as demonstrated by a 3-year study on 777 Swiss seniors[1][2].

• Epigenetic clocks were used to measure the pace of aging, showing up to 4 months of biological age reduction[1][3].

• Additional benefits included:

  • 61% reduction in invasive cancer risk[4]
  • 10% reduction in falls[4]
  • 13% decrease in infection rates[4]

• Sources of omega-3: fish, seafood, rapeseed and flaxseed oil, walnuts, supplements[7][9]

Citations: [1] https://www.sci.news/medicine/omega-3-supplementation-biological-aging-13635.html [2] https://www.news-medical.net/news/20250204/Omega-3-fatty-acids-and-vitamin-D-slow-biological-aging-in-older-adults.aspx [3] https://www.nature.com/articles/s43587-024-00793-y [4] https://www.medonet.pl/leki-od-a-do-z/witaminy-i-mineraly,wystarczy-gram-dziennie--spowolnisz-starzenie-nawet-o-cztery-miesiace,artykul,86261609.html [5] https://www.eurekalert.org/news-releases/1072552 [6] https://www.national-geographic.pl/nauka/kwasy-omega-3-to-pigulka-mlodosci-zwlaszcza-w-polaczeniu-z-witamina-d/ [7] https://dzienniknaukowy.pl/kwasy-tluszczowe-omega-3-wydaja-sie-spowalniac-procesy-starzenia [8] https://translate.google.com/?prev=_t&hl=pl&ie=UTF-8&eotf=1&sl=en&tl=zh-CN [9] https://www.businessinsider.com/taking-omega-3-supplements-may-slow-down-aging-study-2025-2 [10] https://pubmed.ncbi.nlm.nih.gov/36629088/ [11] https://www.sciencedaily.com/releases/2025/02/250204132423.htm

• Figma's Initial Infrastructure Challenges:

  • Figma's monolithic architecture struggled with resource allocation inefficiencies and limited scalability.
  • High traffic spikes from collaborative design workflows required more robust solutions for resource autoscaling and failover.

• Why Kubernetes Was Chosen:

  • Kubernetes' container orchestration capabilities promised better resource management and service isolation.
  • Features like Horizontal Pod Autoscaling (HPA), robust networking via Kubernetes Services, and support for StatefulSets made it an ideal fit for Figma’s needs.
  • The platform also wanted better alignment with cloud-native practices and modern CI/CD workflows.

• Incremental Migration Approach:

  • Step 1: Non-Critical Services: Figma migrated stateless services first, allowing experimentation without risking core functionality.
  • Step 2: Custom Tooling: Internal tooling was built to manage Kubernetes manifests and automate Helm chart creation for standardization.
  • Step 3: Stateful Services: For databases and other stateful components, Figma relied on Kubernetes' StatefulSets and persistent volumes (PVs) to ensure data integrity during the migration.
  • Step 4: Observability Enhancements: Kubernetes-native tools like Prometheus and Grafana were integrated to provide detailed metrics and system insights.

• Key Technical Adjustments During Migration:

  • Service Discovery: Transitioned to Kubernetes-native DNS for internal service communication, replacing legacy methods.
  • Load Balancing: Leveraged Kubernetes Ingress and external load balancers (e.g., NGINX or cloud-native solutions) for traffic routing.
  • Networking Complexity: Resolved challenges around multi-cluster networking using Kubernetes CNI plugins like Calico.
  • Resource Management: Used Resource Quotas and Limits to prevent pod overcommitment and optimize cluster utilization.

• Challenges Faced:

  • Stateful Services: Ensuring zero-downtime migration for databases required careful orchestration of PersistentVolumeClaims (PVCs) and StatefulSets.
  • Networking: Handling cross-region traffic and external dependencies required tweaking Kubernetes Ingress configurations.
  • Resource Constraints: Balancing costs and performance involved tuning cluster-autoscaler configurations and evaluating node pool setups.

• Benefits Realized Post-Migration:

  • Scalability: Kubernetes' HPA allowed Figma to scale pods dynamically based on traffic patterns, ensuring consistent performance.
  • Deployment Efficiency: CI/CD pipelines integrated seamlessly with Kubernetes, enabling faster and more reliable rollouts using tools like Argo CD.
  • Reliability: Self-healing capabilities, such as pod restarts and node failover, reduced downtime during failures.
  • Observability: Improved system monitoring with Kubernetes' native metrics server and integrations with Prometheus and Grafana.

• Future Enhancements Planned:

  • Service Mesh Integration: Adoption of Istio or Linkerd to enhance observability, security (e.g., mutual TLS), and traffic management.
  • Cost Optimization: Further tuning autoscaling policies and resource limits to minimize waste.
  • Edge Improvements: Deploying Kubernetes clusters closer to end-users for reduced latency, potentially using Kubernetes' Cluster Federation.

• Overview of Tesla's Data Infrastructure Challenges:

  • Modern Tesla vehicles generate an enormous volume of telemetry data related to sensor readings, driver behavior, energy consumption, and more.
  • The primary challenge is ingesting, processing, and analyzing this data at scale while maintaining real-time capabilities.

• Kubernetes for Orchestration:

  • Tesla uses Kubernetes to manage containerized microservices across a distributed cloud environment.
  • Kubernetes ensures dynamic scaling to handle fluctuating workloads, providing high availability for critical services.
  • Each microservice is encapsulated in its own container, improving isolation and deployability.

• Kafka for Real-Time Event Streaming:

  • Apache Kafka is the backbone of Tesla’s data pipeline, managing trillions of events daily from globally distributed vehicles.
  • Kafka topics are structured to partition and replicate data efficiently, ensuring fault tolerance and high throughput.
  • Producers (vehicles) send data to Kafka brokers, while consumers (analytics systems, data lakes) process these streams in real-time.

• Data Processing Pipelines:

  • Data from Kafka is ingested into processing systems for real-time analytics, anomaly detection, and predictive maintenance.
  • Stream processing frameworks (e.g., Apache Flink or Kafka Streams) analyze data for immediate feedback.
  • Batch systems handle aggregation and storage in Tesla’s data lake for long-term insights.

• Key Technical Advantages:

  • Scalability: Kubernetes dynamically allocates resources based on the volume of incoming data and computational requirements.
  • Resilience: Kafka’s replication factor ensures that no single broker failure impacts the system.
  • Low Latency: Data streams from Kafka enable Tesla to act on insights in milliseconds, critical for safety and performance monitoring.

• Simplified Management:

  • The platform supports multi-cluster Kubernetes configurations for geographic data segregation.
  • A central control plane monitors system health, manages deployments, and ensures compliance with data regulations.

• Future Goals and Improvements:

  • Enhancing AI-driven analytics to derive deeper insights from vehicle data.
  • Further optimizing Kafka’s cluster topology to improve fault tolerance and reduce operational costs.
  • Expanding edge processing capabilities in vehicles to pre-filter data, reducing bandwidth requirements to the cloud.

• Kubernetes Configuration Drift Issue:

  • Reddit experienced a significant outage on March 13, 2022, during a Kubernetes upgrade from version 1.23 to 1.24.
  • The outage was caused by configuration drift, where unintended changes accumulated over time, leading to inconsistencies across clusters.

• New Platform Abstraction with Declarative APIs:

  • Reddit adopted a declarative approach, leveraging Kubernetes controllers to manage configurations and enforce consistency.
  • The implementation of these controllers enabled Reddit to abstract platform complexities and ensure a uniform deployment environment.

• Centralized Control Plane for Multi-Cluster Management:

  • The team built a centralized control plane to manage multiple Kubernetes clusters effectively.
  • Cluster provisioning time was drastically reduced from over 30 hours to approximately 2 hours.
  • Centralization facilitated standardized configurations and reduced operational overhead.

• Development of Achilles SDK:

  • Achilles, an SDK developed in-house by Reddit, simplified the creation of Kubernetes controllers.
  • It allowed infrastructure engineers to automate and manage resources programmatically without deep Kubernetes expertise.
  • The SDK supported a more proactive approach to problem-solving, preventing drift by design.

• Benefits and Lessons Learned:

  • The new system ensured robust monitoring, minimized manual intervention, and improved scalability.
  • Configuration drift was effectively mitigated, providing a more stable and predictable infrastructure.
  • The experience highlighted the importance of using Kubernetes-native solutions and declarative configurations for managing large-scale deployments.

• Future Goals:

  • Further refinement of the platform to address edge cases and improve developer experience.
  • Continued investment in tools and processes to maintain infrastructure consistency at scale.

MLOps prediction for 2025

MLOps prediction for 2025

MLOps prediction for 2025

RAG will shine even more in 2025

Simple definition of RAG

• Finding Wins Above Replacement: Look for candidates who made a significant impact in their past roles, distinguishing their actions from team efforts. This highlights their talent, agency, and individuality.

• Key Traits to Identify:

  • Creativity: Ability to identify bigger problems and opportunities rather than merely following orders.
  • Resourcefulness & Follow-through: Persistence to complete tasks even when facing obstacles.
  • Vision: A thoughtful, original future vision with coherent life choices.

• Effective Questions to Ask:

  • "Tell me about your best [accomplishment/task]."
  • "If your life was a book, give me the chapter titles from birth till now."

• Chip on the Shoulder: Candidates with a drive to prove themselves can be valuable. Look for those with optimism and resilience rather than deep insecurities or negativity.

• Challenges as Motivation: Present company challenges and assess if candidates are excited by the opportunity to make an impact rather than deterred by imperfection.

• High EQ & Persuasion: Evaluate their ability to adapt communication and influence effectively, especially in group interactions.

• Theory for Excellence: Past excellence in any field (sports, arts, academics) suggests transferable drive and discipline for unrelated roles.

• Understanding Competence: Candidates should know their strengths, weaknesses, and preferred tools or methods.

• Spike Potential: Tailor questions to their profile and assess specific strengths that hint at future excellence.

• Coachability & Openness: Look for candidates open to feedback, willing to improve, and capable of committing even when they disagree.

• Unpretentiousness: Seek candidates who are self-aware, lighthearted, and pleasant to work with.

• Assessment Methods:

  • Use scenario-based interviews, group exercises, or role-playing to evaluate real-time reactions.
  • Gather backchannel references for additional insights.

Participants were asked: "Is your walking speed faster than people of your gender and age?" Based on their answers, they were categorized as "fast walkers" or "slow walkers."

The study included:

• 8,578 obese individuals,
• 9,626 individuals with a large waist circumference,
• 6,742 individuals meeting both criteria.

Summary:

• Overweight individuals who perceive their walking speed as fast have a 30% lower risk of diabetes, along with reduced risks of hypertension and dyslipidemia.
• Subjective assessment of walking speed can serve as a simple and cost-effective tool to identify metabolic health risks.
• Fast walking indicates the good condition of muscles, joints, and the cardiovascular and respiratory systems.
• Previous research has linked slow walking speed to an increased risk of cardiovascular diseases and higher mortality rates in older adults.

• Regular coffee consumption can extend life by an average of 1.8 years, according to researchers from the University of Coimbra.
• Findings are based on a meta-analysis of over 50 studies.
• Benefits of coffee consumption include:
  • Reduced risk of heart disease, type 2 diabetes, and obesity.
  • Improved circulation.
  • Relief from muscle pain.
  • Anti-inflammatory effects due to chlorogenic acids, which act as antioxidants combating free radicals responsible for cellular aging.
• Recommendations:
  • Limit intake to no more than 4 cups per day.
  • Avoid adding sugar and cream.

Summary

🌍 Avoiding Tax Legally in Other Countries

Changing tax residency for half a year may help avoid taxes (but it;s complex and rather recommended for very high earnings). You can move for example to: - United Arab Emirates: No crypto tax. - Germany: No tax on crypto sold after holding for 12 months. - Portugal: Similar tax-free policies for holding over a year.

🔄 What Is Taxed?

Transactions converting cryptocurrency into fiat currency (e.g., PLN, USD) or purchasing goods like property or pizza with cryptocurrency are taxable. Pure crypto-to-crypto transactions are not taxable.

📈 How to Calculate Tax

Calculate the difference between the amount spent to acquire cryptocurrency and the amount earned from its sale. Example: If Bitcoin was bought at $30,000 and sold at $40,000, the taxable income is $10,000.

💰 Tax Rate Overview

• Income up to 1 million PLN is taxed at 19%.
• Income exceeding 1 million PLN incurs an additional 4% solidarity tax, totaling 23% for high earners.

📃 Keeping Records

Tax obligations arise at the moment of converting crypto to fiat or goods, not at the time of withdrawal from an exchange. Keep detailed records to avoid issues during audits or when exchanges request proof of funds.

⚠️ Challenges and Advice

Tax laws in Poland are comprehensive and offer few loopholes. Engaging tax professionals is strongly advised to ensure compliance and minimize errors.

🔄 Deferring Tax Payments in Poland Using Stablecoins

One strategy involves converting crypto profits into stablecoins at year-end and selling them in the following year to postpone taxation. Below is a detailed breakdown of how the strategy works and its limitations.

The Concept

Stablecoins are cryptocurrencies pegged to fiat currencies (e.g., USD or EUR) and have stable values. Using stablecoins in Poland offers a way to legally defer tax payments:

1. End-of-Year Transaction:

   • Convert your cryptocurrency gains (e.g., Bitcoin) into stablecoins like Tether (USDT) or USD Coin (USDC) at the end of the tax year.
   • These transactions, as crypto-to-crypto conversions, are not taxable in Poland.

2. Start-of-Year Sale:

   • In the new tax year, sell the stablecoins for fiat currency (e.g., PLN).
   • The taxable event occurs in the following year, deferring the tax obligation.

Benefits of This Strategy

1. Tax Payment Deferral:

   • Delays the payment of taxes on your crypto gains by shifting the taxable event to the next year.

2. Inflation Advantage:

   • Inflation reduces the real value of money over time, decreasing the actual financial burden of the deferred tax.

3. Liquidity Management:

   • Funds remain accessible as stablecoins, which can be reinvested or used in decentralized finance (DeFi) during the deferral period.

How Long Can This Be Done in Poland?

• The strategy can be legally repeated annually for up to 15 years.
• After 15 years, the deferred gains may be treated differently or trigger tax liabilities due to long-term reporting requirements. It's important to monitor evolving tax regulations in Poland to ensure compliance.

Key Considerations

1. Documentation:

   • Maintain detailed records of all transactions, including dates, values, and stablecoin transfers, for tax compliance and audits.

2. Stablecoin Selection:

   • Choose stablecoins with strong pegs to fiat currencies to avoid price fluctuations that may affect gains or losses.

3. Regulatory Changes:

   • Polish tax laws are subject to change. Always confirm that the strategy remains valid before executing it.

Example

• Year 1 (2023):

  • Bitcoin bought for PLN 50,000.
  • Sold for PLN 150,000 at the end of 2023.
  • Proceeds converted to USDT (not taxable in Poland).

• Year 2 (2024):

  • USDT sold for PLN 150,000 in January.
  • Taxable gain of PLN 100,000 is reported in the 2024 tax year.

Limitations

1. Short-Term Transactions:

   • If stablecoins are sold within the same year as the crypto-to-stablecoin conversion, the tax deferral benefit is lost.

2. Exchange Fees:

   • Frequent crypto-stablecoin conversions may incur exchange fees, slightly reducing net gains.

3. Regulatory Risks:

   • Future changes to tax laws or stablecoin regulations could impact the strategy's viability.

This strategy allows you to legally defer cryptocurrency taxes for a significant period, maximizing your financial flexibility and leveraging stablecoin stability. Always consult a tax professional for tailored advice and compliance.

Why Gitpod is Leaving Kubernetes

Gitpod has decided to transition away from Kubernetes for managing cloud development environments, opting instead for a custom-built solution better suited to their needs. While Kubernetes is powerful for orchestrating stateless application workloads, Gitpod identified several challenges that made it less ideal for their dynamic, stateful workloads.

Key Challenges of Kubernetes

• Resource Overhead: Kubernetes introduces significant complexity and resource consumption, which is inefficient for scaling ephemeral development environments.

• Latency in Scaling: The time required to scale pods and handle stateful workloads can slow down developer workflows that demand near-instant provisioning.

• Stateful Workloads: Kubernetes is designed for stateless applications, and adapting it for stateful environments adds operational complexity.

• Cost Inefficiency: Running dynamic workloads on Kubernetes incurs higher operational costs due to the constant need for scaling and resource orchestration.

• Security Concerns: Managing multi-tenant security on Kubernetes is challenging, requiring considerable effort to ensure workload isolation and permission control.

• Operational Complexity: Maintaining Kubernetes clusters at scale involves a significant operational burden, including updates, monitoring, and configuration management.

Gitpod is now focusing on Gitpod Flex, a new solution tailored to better meet the demands of developers, offering improved scalability, efficiency, and simplicity.

The introduction of the Image Volume Source feature in Kubernetes 1.31 allows MLOps practitioners to mount OCI-compatible artifacts, such as large language model weights or machine learning models, directly into pods without embedding them in container images. This streamlines model deployment, enhances efficiency, and leverages OCI distribution mechanisms for effective model management.

Article about remote work

In essence, this article is about:

1) Training a sample model and uploading it to an S3 bucket:

```python from sklearn.datasets import load_iris from sklearn.model_selection import train_test_split from sklearn.linear_model import LogisticRegression import joblib

Load the Iris dataset

iris = load_iris() X, y = iris.data, iris.target

Split the data into training and testing sets

X_train, X_test, y_train, y_test = train_test_split(X, y, test_size=0.2, random_state=42)

Train the logistic regression model

model = LogisticRegression(max_iter=200) model.fit(X_train, y_train)

Save the trained model to a file

joblib.dump(model, 'model.pkl') ```

1. Creating a sample Zappa config, because AWS Lambda doesn’t natively support Flask, we need to use Zappa, a tool that helps deploy WSGI applications (like Flask) to AWS Lambda:

```json { "dev": { "app_function": "app.app", "exclude": [ "boto3", "dateutil", "botocore", "s3transfer", "concurrent" ], "profile_name": null, "project_name": "flask-test-app", "runtime": "python3.10", "s3_bucket": "zappa-31096o41b" },

"production": {
    "app_function": "app.app",
    "exclude": [
        "boto3",
        "dateutil",
        "botocore",
        "s3transfer",
        "concurrent"
    ],
    "profile_name": null,
    "project_name": "flask-test-app",
    "runtime": "python3.10",
    "s3_bucket": "zappa-31096o41b"
}

} ```

1. Writing a sample Flask app:

```python import boto3 import joblib import os

Initialize the Flask app

app = Flask(name)

S3 client to download the model

s3 = boto3.client('s3')

Download the model from S3 when the app starts

s3.download_file('your-s3-bucket-name', 'model.pkl', '/tmp/model.pkl') model = joblib.load('/tmp/model.pkl')

@app.route('/predict', methods=['POST']) def predict(): # Get the data from the POST request data = request.get_json(force=True)

# Convert the data into a numpy array
input_data = np.array(data['input']).reshape(1, -1)

# Make a prediction using the model
prediction = model.predict(input_data)

# Return the prediction as a JSON response
return jsonify({'prediction': int(prediction[0])})

if name == 'main': app.run(debug=True) ```

1. Deploying this app to production (to AWS):

bash zappa deploy production

and later eventually updating it:

bash zappa update production

1. We should get a URL like this:

https://xyz123.execute-api.us-east-1.amazonaws.com/production

which we can query:

curl -X POST -H "Content-Type: application/json" -d '{"input": [5.1, 3.5, 1.4, 0.2]}' https://xyz123.execute-api.us-east-1.amazonaws.com/production/predict

You may use uv in production, but there may be still some undiscovered quirks.

About uv Python packaging tool

The blog post by Cliff Malmborg from Loft Labs discusses optimizing Kubernetes costs using multi-tenancy and virtual clusters. With Kubernetes expenses rising rapidly at scale, traditional cost-saving methods like autoscaling, resource quotas, and monitoring tools help but are not enough for complex environments where underutilized clusters are common. Multi-tenancy enables resource sharing, reducing the number of clusters and, in turn, management and operational costs.

A virtual cluster is a fully functional Kubernetes cluster running within a larger host cluster, providing better isolation and flexibility than namespaces. Unlike namespaces, each virtual cluster has its own Kubernetes control plane, so resources like statefulsets and webhooks are isolated within it, while only core resources (like pods and services) are shared with the host cluster. This setup addresses the "noisy neighbor" problem, where workloads in a shared environment interfere with each other due to resource contention.

Virtual clusters offer the isolation benefits of individual physical clusters but are cheaper and easier to manage than deploying separate physical clusters for each tenant or application. They also support "sleep mode," automatically scaling down unused resources to save costs, and allow shared use of central tools (like ingress controllers) installed in the host cluster. By transitioning to virtual clusters, companies can balance security, isolation, and cost-effectiveness, reducing the need for multiple physical clusters and making Kubernetes infrastructure scalable for modern, resource-demanding applications.

Gold has risen in price by 33% since the beginning of the year and is now worth PLN 10,780 per ounce. This is almost the best year for this precious metal in 45 years.

It may be over of IP BOX (5%) in 2025.

This article (which can be viewed using a paywall remover) shows that even if someone does not deal directly with code, the court may think otherwise:

Fiskus i NSA nie pozwalają na niższą stawkę ryczałtu W sprawie, która doszła do NSA, spór ze skarbówką zaczął się od wniosku o interpretację informatyka prowadzącego jednoosobową działalność. Napisał, że zajmuje się projektowaniem i rozwojem technologii informatycznych dla sieci i systemów komputerowych lub ich poszczególnych składowych/komponentów. Świadczy też usługi pomocy technicznej. Szczegółowo opisał wszystkie czynności. Podkreślił też, że do zakresu jego obowiązków nie należy tworzenie oprogramowania. Dlatego uważa, że ma prawo do niższej stawki ryczałtu. Fiskus miał jednak inne zdanie. Uznał, że informatyk powinien płacić 12 proc. ryczałt, ponieważ „okoliczność, że do zakresu obowiązków podatnika nie należy tworzenie oprogramowania komputerowego, nie jest wystarczającą przesłanką do uznania braku związku świadczonych usług z oprogramowaniem”.

Informatyk zaskarżył interpretację, przegrał jednak zarówno w pierwszej, jak i drugiej instancji. Wojewódzki Sąd Administracyjny w Gliwicach zauważył, że z wniosku o interpretację wynika, iż świadczone usługi są związane z rozwojem systemu SAP. Ten system jest oprogramowaniem wspomagającym prowadzenie przedsiębiorstwa. Opisane usługi są więc niewątpliwie związane z oprogramowaniem – uznał gliwicki WSA. Za szerokim rozumieniem pojęcia „usługi związane z oprogramowaniem” opowiedział się też NSA. Podkreślił, że nie chodzi tylko o programowanie, ale również inne czynności. Także te, które wykonuje przedsiębiorca.

Sąd wymienił wszystkie obowiązki informatyka i po prostu stwierdził, że są to usługi związane z oprogramowaniem. Po NSA spodziewałbym się głębszej analizy i dokładnego określenia, które z wymienionych czynności spełniają to kryterium. Miejmy nadzieję, że kolejne orzeczenia będą wnikliwsze. I po głębszych rozważaniach może okaże się, że to jednak podatnicy mają rację – podsumowuje Piotr Sekulski

In September, employers in Poland published 12% more job offers y/y (288 thousand).

The increase has been going on for 4 months, and now it has reached the highest level since March 2022. The largest increase in the number of job offers is in medical professions (24%) and manual workers (13%). Decrease among financiers (-15%), HR specialists (-10%) and lawyers (-7%). In IT, the number of offers increased by 5%, and in marketing and sales by 1%.

Good advice for the presenters using macOS

Mental disorders are indirectly contagious – i.e. negative emotional and behavioral patterns that cause illness are transferred even to friends of people with disorders, a study in Finland involving 700,000 people has shown.

The data showed that having friends diagnosed with mental disorders in the 9th grade of secondary school increased the risk of developing mental disorders later in life, such as mood swings, anxiety and eating disorders, by up to 18%.

Drinking 3 cups of coffee or 200-300 mg of caffeine a day can halve the risk of diseases such as type 2 diabetes, coronary artery disease and stroke, researchers from Suzhou University in China, in collaboration with Swedish scientists, have shown.

Moderate caffeine consumption may protect cardiovascular health, regardless of age, gender, smoking or diet. The study is based on data from over 300,000 people from the UK Biobank, collected over 11 years.

The essence of cutting AWS data transfer costs by 99% is to use Amazon S3 as an intermediary for data transfers between EC2 instances in different Availability Zones (AZs). Instead of direct transfers, which incur significant costs, you upload the data to S3 (free upload), and then download it within the same region (free download). By keeping the data in S3 only temporarily, you minimize storage costs, drastically reducing overall transfer expenses.

Infopiguła:

Liczba Polaków zarabiających ponad 10 tys. zł / mc wzrosła w 2022 r. o 51% rdr., do 1,5 mln osób. Na koniec 2022 r. było w Polsce 90 tys. milionerów dolarowych, 10% mniej niż rok wcześniej.

Pensje zarabiających ponad 10 tys. wzrosły o 10% do ok. 375 mld zł. Głównym czynnikiem była wysoka inflacja, ale też napływ Ukraińców z dobrymi zarobkami w korporacjach.

Liczba osób z zarobkami 20-50 tys. zł / mies. wzrosła o 38% do 440 tys., tych z zarobkami między 50 a 83 tys. zł wzrosła o 1% do 84 tys., a osób z zarobkami ponad 83 tys. zł (czyli 1 mln rocznie) spadła o 5% do 35 tys. O prawie 2% wzrosła liczba osób z majątkiem ponad 50 mln $.

In this case, IaC is favored over using EKS directly or manually deploying on EC2

Why use EKS

Cost of EKS

Benefits of using Kubernetes on AWS: - scalability - cost efficiency - high availability

special methods = magic methods = dunder methods

Opening URL using Python's webbrowser module

Sample .devcontainer/devcontainer.json:

json { "name": "Global", "build": { "context": "..", "dockerfile": "Dockerfile" }, "containerEnv": { "PYTHONPATH": "." }, "customizations": { "vscode": { "settings": { "extensions.verifySignature": false }, "extensions": [ "GitHub.copilot", "ms-python.vscode-pylance", "ms-python.python", "eamodio.gitlens" ] } }, "initializeCommand": "/bin/bash -c '[[ -d ${HOME}/.aws ]] || { echo \"Error: ${HOME}/.aws directory not found.\"; exit 1; }; [[ -f ${HOME}/.netrc ]] || { echo \"Error: ${HOME}/.netrc file not found.\"; exit 1; }; [[ -d ${HOME}/.ssh ]] || { echo \"Error: ${HOME}/.ssh directory not found.\"; exit 1; }; echo \"\n> All required mounts found on the host machine.\"'", "onCreateCommand": { "hadolint": "apt-get update && apt-get install wget -y && wget -O /bin/hadolint https://github.com/hadolint/hadolint/releases/download/v2.12.0/hadolint-Linux-x86_64 && chmod u+x /usr/bin/hadolint", "precommit": "pip install pre-commit" }, "updateContentCommand": "/bin/bash -c 'if grep -A 2 \"machine gitlab.com\" ~/.netrc | grep -q \"password\" && GITLAB_TOKEN=$(grep -A 2 \"machine gitlab.com\" ~/.netrc | grep -oP \"(?<=password ).*\" | tr -d \"\\n\") && [ -n \"$GITLAB_TOKEN\" ]; then echo \"\n> Token found in ~/.netrc\"; else read -sp \"\n> Enter your GitLab token: \" GITLAB_TOKEN && echo; fi; echo \"export GITLAB_TOKEN=$GITLAB_TOKEN\" >> ~/.bashrc && . ~/.bashrc && poetry config http-basic.abc __token__ $GITLAB_TOKEN'", "postCreateCommand": ". ~/.bashrc && curl -s --location 'https://gitlab.com/api/v4/projects/12345/repository/files/.pre-commit-config.yaml/raw?ref=main' --header \"PRIVATE-TOKEN: $GITLAB_TOKEN\" -o .pre-commit-config.yaml", "postAttachCommand": "/bin/bash -c '. ~/.bashrc && read -p \"\n> Do you want to update the content of devcontainer.json? (y/n): \" response; if [[ \"$response\" == \"y\" ]]; then curl -s --location \"https://gitlab.com/api/v4/projects/12345/repository/files/devcontainer.json/raw?ref=main\" --header \"PRIVATE-TOKEN: $GITLAB_TOKEN\" -o .devcontainer/devcontainer.json; else echo \"\n> Skipping update of devcontainer.json\"; fi'", "mounts": [ "source=${localEnv:HOME}/.aws/,target=/root/.aws/,type=bind,readonly", "source=${localEnv:HOME}/.netrc,target=/root/.netrc,type=bind,readonly", "source=${localEnv:HOME}/.ssh/,target=/root/.ssh/,type=bind,readonly" ] }

Some more of my recent learning with devcontainer.json (its Dev Container metadata):

• Interactive commands (those waiting for user input like read) do not display the input request in (at least onCreateCommand and postCreateCommand sections), so it is better to keep them in updateContentCommand or postAttachCommand.
• If there are 2 read commands in a single section, like updateContentCommand, only the 1st one is displayed to the user, and the 2nd one is ignored.
• When I put a read command within a dictionary (with at lest 2 key/values) of postAttachCommand, the interactive command wasn't being displayed.
• We need to use /bin/bash -c to be able to use read -s (the -s flag) which allows for securely passing the password so that it does not stay in the VS Code console. Also, I had trouble with interactive commands and if statements without it.
• Using "GITLAB_TOKEN": "${localEnv:GITLAB_TOKEN}" does not easily work as it is looking for GITLAB_TOKEN env variable set locally on our host computers, and I believe no one does it.
• The dictionary seems to be executing its scripts in parallel; therefore, it is not easily possible to break down long lines which have to execute in a chronological sequence.
• JSON does not allow for human-readable line breaks; therefore, indeed, it seems impossible to improve the long one-liners.
• The files/folders mentioned within mounts need to exist locally (otherwise, Docker container build fails). They are mounted before any other section. Technically, we can protect ourselves with the following command to find an extra message in VS Code container logs:

json "initializeCommand": "/bin/bash -c '[[ -d ${HOME}/.aws ]] || { echo \"Error: ${HOME}/.aws directory not found.\"; exit 1; }; [[ -f ${HOME}/.netrc ]] || { echo \"Error: ${HOME}/.netrc file not found.\"; exit 1; }; [[ -d ${HOME}/.ssh ]] || { echo \"Error: ${HOME}/.ssh directory not found.\"; exit 1; }'",

Other option is to get rid of the error completely, but this creates files on the host machine; therefore, it is not an ideal solution:

json "initializeCommand": "mkdir -p ~/.ssh ~/.aws && touch ~/.netrc",

I would also simply put the following:

bash /bin/bash -c 'read -p 'Type a message: ' -t 10 && echo Attach $REPLY'