This article seems to be the source organiser.org/2026/06/15/358… - from the organizer ie the mouthpiece of the RSS. No sources cited in the article. Misinfo spread from pure vibes

Interesting choice to give your fire type starter no fire moves

AGI is here

Interviewed some candidates for a devOps role today Was really surprised by the high quality of candidates - all of them were good really hard to pick just one Guess in a bad market you can really be picky eh 😅

We would really like to slow down development but china forced our hand The $$$ motive certainly is not a factor

Welp my alma mater is in the news for all the wrong reasons

"Rebuilt in go for speed" Rendering text on a terminal 30% faster after waiting 10s for a model response. Cmon guys - the language is not the issue!

Sadly it is human behaviour. Let's say u r 20 years into a job with limited growth oppurtunities(Happens as u rise in every company). If thr is a junior capable of doing u r work. Will u promote them & increase u r competition or delay their growth till u manage a promotion?

The obsession with becoming a dollar millionaire is a vanity metric that only matters if your end goal is importing luxury goods or retiring in the US. For the vast majority of wealth creators in India, domestic Purchasing Power Parity (PPP) is what actually dictates your standard of living and financial stature. True wealth is built on how far your capital goes in the economy you actually live in, not an arbitrary foreign benchmark!

Love how the email is perfectly vague giving absolutely no details. If you believe this I have a bridge to sell you

Imagine a world where openai implodes and we have to go back to pip installing

Day 4/7 of Java Concurrency - wait(), notify(), notifyAll() Every Java object has a monitor - a built-in lock waiting room. The API is simple - call wait() to release the lock and go to sleep. Another thread calls notify() to wake one sleeping thread up. notifyAll() wakes all of them. You must hold the object’s lock to call these methods. Otherwise you get an IllegalMonitorStateException. Never use if with wait() - The JVM is allowed to wake your thread for no reason at all - these are called spurious wakeups. Always use a while loop to re-check the condition after every wakeup. notify() wakes one random thread. If that thread doesn’t care about the condition that changed, you can lose the wake and potentially deadlock. Almost always use notifyAll() - which wakes All waiting threads In general we use higher level abstractions for synchronisation, but its good to know about the absolute fundamentals!

Do your 16k lines of code. Get your demo out and get your user/investors. Hire employees to fix the slop ezpz

Day 3/7 of Java Concurrency - Compare and set - the secret sauce behind lock free data structures Lock free data structures manage to avoid race conditions without using any locks at all - how is this even possible? Enter compareAndSet, a method exposed by AtomicReference. The API is very straightforward - ref.compareAndSet(expected, newValue) -> if the current value is expected, then it sets it to newValue, otherwise if another thread updated it - we get a return false. No waiting, no blocking. The key pattern that makes this useful is running it in a loop, we keep comparing and setting in a loop till the thread eventually gets one return true, and we exit! Look at this lock free implementation of a stack that can handle concurrent reads and writes!

Day 2/7 of Java Concurrency - Semaphores We all know about locks for mutual exclusion. But what if we want to allow N threads in at once? Semaphores solve this exact problem - the api is quite simple - you initialize with a number of "permits" Semaphore semaphore = new Semaphore(n, true); The key methods - acquire() - takes a permit (blocks if none available) release() - returns a permit the boolean parameter is for fairness - true = fair (FIFO) false = no fairness guarentee (but faster!) Any thread can release a permit. Unlike a lock, the thread that acquires doesn't have to be the one that releases - allowing signaling between threads.

Happy Pi day This is still the craziest place pi shows up - 2 bouncing balls This is a must watch! youtube.com/watch?v=abv4Fz7o…

What writing code with AI feels like

Day 1/7 of Java Concurrency - Double checked locking We all know about the singleton pattern, but how can we make it safe in a multithreaded environment? An obvious solution would be to add a synchronized block around if(instance == null) { instance = expensiveIntialize(); } But then we would need to accquire a lock for all calls of getInstance. A second solution would be to do a null check outside and only synchronize the initialization if(instance == null) { synchronized(obj) { instance = expensiveIntialize(); } } But this doesnt work either as two threads waiting on the synchronized block will both initialize the object. So we need to do a 2nd null check within the synchronized (obj) to prevent double creation. Also this wont work without a memory barrier (if thread 1 writes instance = <Instance>, thread 2 may not see it without a memory barrier). -> thats where the instance has to be volatile. This pattern is common enough to have a name - Double Checked Locking The solution:

Literally all "prompting" skills keep dying Think step by step Ultrathink Personas ("You are a staff software engineer") ... the list goes on and on Meanwhile learning to code has never been more useful so you can catch bs from models

with AI, I can finally stop coding and do things i am really passionate about - like scrum and agile product management