😱😱😱 And just like that, it’s completely VANISHED from the media.
A sitting congressman, Ted Lieu, said on the record the Epstein files are being blocked because they show Trump raped and threatened to kill children.
Lets make this viral again 👇
My friend went to an indie hacker meetup this week and said this:
"i went to indie hacker meetup
so what’s really interesting is that almost everyone is super focused on development.
they build these whole spaceships that generate code, review it, make all kinds of reports, analytics, and so on.
one guy built an entire factory: he has a list of ideas, and agents generate the landing page, the saas, the analytics, and pull everything into one dashboard. straight-up sci-fi.
and they focused optimize all of it like crazy.
and you can really see how comfortable that is for them.
but the most interesting part is that almost none of them have money or traffic.
and nobody knows where to get either one.
you often hear something like, yeah, i should probably do on marketing, but first i’ll finish my super system and then i’ll start.
or in best i would need to make agent that will post to instaram automatically
before, the classic programmer would spend a year writing code, tests, preparing for scale in the basement, and not show anything to anyone.
now it’s even worse: the amount of useless aislop nobody needs has grown massively."
Mad sequence. Rice wins ball cleanly. Vitinha hand balls it to take it away from rice. Vitinha holds rice leg. Rice clips neves but doesn’t stop him. Saka wins the ball cleanly off neves.
Referee… free kick to PSG. Investigate this guy. Check his property portfolio next year.
Bayangin u rekomen buat masukin $MANTA
Atau u secara publik mengakui ngorbanin follower u jadi exit liquidity biar bisa mengeruk duit dipucuk
Nah sekarang bayangin ada team yang proper, doing proper due diligence, terus bikin rekomendasi investasi
Sekarang tebak yang masuk penjara yang mana?
Bayangin dulu aja, kali2 ini semua cuma mimpi
Cardiologist wins 3rd place at Anthropic's hackathon. Out of 13,000 applications. Built in 7 days by Michał Nedoszytko MD. Coded day and night - in the hospital, in the cloud, while flying from Brussels to San Francisco.
A few years ago, it would have been impossible for a doctor to build this alone in just a couple of days. AI changed that.
The project is called https://t.co/wAliajqjVF. It is an AI agentic care platform for patients. Including reverse AI scribe it is a companion that guides the patient from the moment they leave the doctor's office.
Powered by the massive context window of Opus 4.6, it allows patients to explore their full medical history, connected devices, Evidence Based resources and external data sources — all in one place.
Today, the barrier to entry has vanished; even a practicing physician can build an application from scratch.
To call yourself a “full-stack” developer in 2024, you must be able to:
- Build frontends
- Build backends
- Provision cloud infrastructure
- Handle UX in Figma
- Maintain efficient CI/CD pipelines
- Create 3D art in Blender
- Manage projects with Scrum
- Attend daily standup meetings without leaving the zone
- Make YouTube videos
- Train transformer models from scratch
- Code live on Twitch for 14 hours straight
- Run a side hustle with at least 10K MRR
- Tweet about cold plunges and fasting
- Beat the stock market with algotrading
- Deploy shit with Kubernetes
- Achieve the Ballmer Peak daily
- Invoke syscalls on Linux
- Optimize for ARM-based CPU architectures
- Publish research papers on quantum algorithms
- Maintain mental health while doing all of the above
Did I miss any?
Bekerja itu sulit. Menganggur juga sulit.
Jadi medioker itu sulit. Berjuang mencapai excellence juga sulit.
Bertahan di kerjaan yang lo benci itu sulit. Resign dan career switching juga sulit.
Pilih kesulitan yang mau dan mampu lo hadapi.
Small software companies shouldn't be so concerned with the threat from overfunded startups or huge competitors because they're fundamentally building a different kind of software. Full podcast: https://t.co/tUry3ThXDO
Seorang pemuda bernama Addril (22) nekat membobol saldo kartu multi trip (KMT) commuter line (KRL) milik PT Kereta Api Indonesia (KAI).
Pelaku berhasil menyusup ke dalam situs keuangan PT KAI secara otodidak setelah melihat tayangan YouTube.
Bermodalkan ponsel, pelaku hanya membutuhkan waktu 2 hari untuk melancarkan aksinya.
Adapun modus pelaku adalah dengan cara mengisi saldo KMT menggunakan aplikasi C-Access dan HttpCanary dengan metode pembayaran melalui GoPay.
"Jadi, dia (tersangka) ini mengubah sistem aplikasi C-Access sehingga pembayaran atau tagihan administrasi hanya Rp 1 (satu rupiah) setiap top up. Nah pelaku ini mendapatkan saldo top up sebesar Rp12.414.998 dari 25 kali top up dengan pembayaran Rp 25 perak," kata Kapolres Metro Depok, Kombes Arya Perdana kepada wartawan, Senin (4/3).
Kasus ini terungkap setelah PT KAI curiga dengan kejanggalan sistem transaksi dalam sistem keuangan mereka.
"Ini awalnya laporan PT KAI yang melihat kok saldonya tidak sesuai dengan apa yang diisikan, ada ketidak cocokan. Jadi mereka punya satu sistem yang melihat ada transaksi yang mencurigakan dalam data pengisian atau top up," katanya.
Sementara itu, Addril mengaku dirinya baru kali ini melakukan aksi peretasan. Ia berdalih melakukan aksinya karena iseng.
"Saya ini pencinta kereta, iseng aja, lagi pingin naik kereta biar gratis," katanya.
Addril juga mengaku, dirinya aktif mengunggah video tentang kereta di TikTok.
Meski begitu, Ia membantah jika dirinya menjual sederet KMT yang telah Ia retas tersebut.
"Nggak, nggak ada yang saya jual. Ini cuma buat pribadi aja," katanya.
Sumber : https://t.co/ciSuMbHkr6
I ended my time at @Meta as a director.
But I started as an engineer on FB Chat.
Everything about it was broken — we had to rewrite it.
And while the effort to fix it is one the projects that led to @reactjs, the most important fix was far simpler...
Here’s the full story:
—
I worked on Facebook Chat for several years, both on the front end and the infrastructure.
Before the major effort to redo the UI, FB Chat was super broken and we had no idea why.
We got tons of bug reports about Chat being broken every day, but we noticed an odd pattern in the data: the volume of reports didn’t match the volume of usage. It was time-shifted from the peaks we’d see in the US.
We didn’t know what was wrong, but we knew the code was a mess.
We set about rewriting both the front-end and the back-end in an effort to fix it.
The front-end rewrite pulled in a whole team of amazing engineers and became one of the big threads that led to @reactjs
In the public eye, we portrayed this project as the one that ultimately fixed Chat.
And the way I’ve usually told it, fixing Facebook Chat and the birth of React are the same story.
But no framework was going to fix the worst problem with Chat.
—
During the time we were working on the Chat rewrite, we were also replacing the original Erlang backend with one written in C++.
This was probably a good move, but the problem wasn’t with Erlang either.
Our initial spec for the new backend didn’t say much about observability, but it was an important feature, and the rewrite forced us to rebuild it.
Little did we know this would lead us to the root cause of our problems…
When we finally gained insight into our deliverability data, we were able to cut it by region.
We noticed Chat was really popular in India. This was before WhatsApp, at a time when SMS wasn’t reliable.
Eventually we pinpointed a region in India where one specific DNS provider was giving out the wrong IP addresses for our Chat servers.
So when people went to use Chat, they would sometimes get a notification that they had a message, and then it would disappear.
Or they’d send a message and it would get lost. All because they were connecting to the wrong IP address.
That was it!
None of the sexy new tech we were working on was going to solve that problem.
Ever.
—
Instead, the solution was to build observability that allowed us to track end-to-end message delivery.
In the end, we could start with a broad cut of our data by country or web browser, and then zoom all the way in to look at what happened to a specific message for a specific user.
Once we pinpointed that the problem was with a DNS server, the matter was resolved with a quick phone call. I don’t know what they did, but I imagine it was something like turning it off and turning it on again.
We sometimes talk about observability as if it’s enough to buy a product like Datadog and just look at the pretty graphs.
Sure, that’s a start.
But true observability is a feature that needs to be built— painstakingly, iteratively, by-definition starting with a shot in the dark.
—
These days, it has become fashionable to poo-poo the idea of being data-driven.
People point out that measurement can distort the phenomenon that is being observed.
They want to make processes “data-informed.”
But this seems like silly backlash against the only rigorous standard in all of software engineering:
That we hold ourselves to an objective standard.
We measure how long things take, how many errors we encounter, how often a process successfully runs to completion.
So here’s what this experience taught me about observability:
When an issue happens in production, time-box the investigation.
Sure, take a few hours to try and figure it out by looking in the logs and inspecting the code.
But if you’re coming to the end of the day and you still don’t have a fix, then push a PR that adds logging.
The first one may be just a guess, but it will begin a process that leads to the truth.
And that is what we should all ultimately be striving for.
—
For more engineering tips and stories, follow me @dmwlff