Yet Another Tech Poster

MAANG Software Engineer | Learning about LLMs and scaling models

[Yet Another Tech Poster @YATPoaster]

We would really like to slow down development but china forced our hand

The $$$ motive certainly is not a factor

[Anthropic @AnthropicAI]

Our internal data shows Claude is accelerating AI development—a possible path to recursive self-improvement, or AI autonomously building a more capable successor.

It’s happening faster than we thought, and the implications deserve greater attention. https://t.co/OVVPJO7VQx

[Yet Another Tech Poster @YATPoaster]

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

[D4rsh🦅 @d4rsh_tw]

IIT Hyderabad's research website got hacked

[Yet Another Tech Poster @YATPoaster]

@AnthropicAI I cant be the only one who misread it as "confidently submitted" right :P

[Yet Another Tech Poster @YATPoaster]

"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!

[Gemini CLI @geminicli]

Transitioning Gemini CLI users to Antigravity CLI

We are unifying our efforts around a single harness and platform, Google Antigravity with four distinct surfaces:

• Antigravity 2.0
• Antigravity CLI
• Antigravity SDK
• Antigravity IDE

This will allow us to move faster and give you a streamlined experience wherever you do your best work.

Rebuilt in Go for speed, Antigravity CLI is available today and brings robust multi-agent orchestration and asynchronous workflows to your terminal.

Important things to know:
1. If you are using Gemini CLI through your Google one account (Google AI Pro or AI Ultra) or through Gemini Code Assist for individuals (free offering) we will be helping you migrate your workflows over the next 30 days.

2. No action required for Enterprise users. Enterprise plans and API keys will continue to be supported in Gemini CLI.

Read the full details in our blog post → https://t.co/IqvqDt9XLn

[vauvalman @bruceootham]

@PackBropagated 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?

[Yet Another Tech Poster @YATPoaster]

@OpenAI You are absolutely right - you should drive into that ditch, its not just brave - its bold

[Yet Another Tech Poster @YATPoaster]

@Fried_rice I dont know why anthropic should be mad, coding is "solved" and code is "free" after all

[Yet Another Tech Poster @YATPoaster]

@SumitM_X https://t.co/VSxlo01RWP

Worth a read
In 2012 they were able to handle 1M+ connections per host. Erlang and the underlying BEAM architecture is so fascinating

[Icons of India @ICONSIndiaIN]

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!

[Yet Another Tech Poster @YATPoaster]

@SumitM_X I dont think Objects.isNull can cause a memory leak, you would probably nead to take a heap dump (will pause the prod service for a few seconds) and investigate

[Yet Another Tech Poster @YATPoaster]

@claudeai If its still unsafe to use without a sandbox, bypass permissions still seems better (and the danger is half the fun)

[Yet Another Tech Poster @YATPoaster]

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

[Satakshi @satakshi_ai]

First in my bloodline to get 1 million USD offer. Feeling blessed 🥳🍾

[Yet Another Tech Poster @YATPoaster]

@ptr_to_joel This is the kind of “prod issue” i would be ashamed to mention to anyone

[Yet Another Tech Poster @YATPoaster]

@anothercohen Recognised this face, she posted this unironically

[Selin Kocalar @kocalars]

One interesting observation I’ve noticed is a lot of top founders did oddly strong at math from a young age.

[Yet Another Tech Poster @YATPoaster]

@SumitM_X In rebase all 50 of your commits are replayed one by one onto the head commit.
I have had good success with squashing to 1 commit and then rebasing that one commit onto main (ugly but easier to reason about)
At that point merge is fine too honestly (similar complexity)

[Yet Another Tech Poster @YATPoaster]

@joelgrus Oh i am out of the loop what else do they own other than the current accquisition (astral et al)

[Yet Another Tech Poster @YATPoaster]

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

[Astral @astral_sh]

Astral has entered into an agreement to join OpenAI as part of the Codex team.

https://t.co/UkFATfFpop

[Yet Another Tech Poster @YATPoaster]

@OpenAINewsroom @astral_sh Damn son we can now start OSS software with the hope of a fat exit with $$$

[Yet Another Tech Poster @YATPoaster]

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!

[Yet Another Tech Poster @YATPoaster]

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!

[Yet Another Tech Poster @YATPoaster]

@SumitM_X public String getUserName(User user) {
if (user == null) {
return "No User";
}

String name = user.getName();
if (name == null) {
return "No Name";
}

return name.toUpperCase();
}

Prefer using guard clauses, much more readable flat code