Funny how some people get triggered by this. If you read the whole thing, I actually explain how fucking dumb and clueless LLMs still are once you go past boilerplate. You basically need to keep them in check constantly, even for a pet project like mine. I'm not celebrating anything here, just sharing my journey, the fun and frustrations I've had, going through the stages of vibe-coding: from god-mode euphoria to realizing how deceiving the first rush is.
But I do believe we'll get to the point they will replace more and more engineers. yes, I don't know how fast, I don't know if LLM will be able to reach that point. But eventually, all that money in research will get somewhere I believe.
Coming from Clojure, I get a high level impression that Java is nice for libraries. They're generally pleasant to interact with. OO gives some nice logical organization to the library "API". But I don't get the impression it's great for application development and "green field" projects.
Granted I've never worked with Java "properly" with the whole IDE experience. Just looking at code it's extremely verbose and seems like it'd be really not fun to refactor.
I built LazySSH out of a personal need. I was managing 40+ servers, and even with ~/.ssh/config, it became painful to remember aliases, edit entries, and stay organized.
LazySSH is a terminal-based, interactive SSH manager with a simple, keyboard-driven UI. It lets you:
- Browse and manage servers from your ~/.ssh/config
- Add, edit, pin, ping, or delete entries interactively
- Fuzzy search, tag, and sort servers
- SSH into any host instantly with one keypress
More features are coming soon: file copy (no more long scp commands), port forwarding, and SSH key management.
As I understand it, this is a dataset of claimed causation. It should contain vaccines->autism, not because it's true, but because someone, in public, claimed that it was.
So, by design, it's pretty useless for finding new, true causes. But maybe it's useful for something else, such as teaching a model what a causal claim is in a deeper sense? Or mapping out causal claims which are related somehow? Or conflicting? Either way, it's about humans, not about ontological truth.
Stream | Multiple Positions | Amsterdam (NL), Skopje (Macedonia) | Boulder, CO (US) | Toronto (Canada)) | Remote possible | Full Time | Visa Sponsorship
We are consistently hiring backend engineers ranging from Senior level to Staff / Lead / Director / Principal Go engineers.
If you have experience with a different tech stack, we offer a 10-week onboarding program to train you in Go, scaling and other key topics: https://tinyurl.com/2u5x9f9w
We’re also hiring for:
* Staff Python Engineer – Open Source Video/Voice AI Library
* Senior React Native SDK Engineer
* Staff Product Designer
* WebRTC SFU Engineer
* Director of Information Security
At Stream, we use Go for our video SFU, chat API, Moderation and Feeds, serving high traffic from major apps like Strava, Nextdoor, Patreon, and Midjourney. Our tech stack: Go, CockroachDB, RocksDB, WebRTC, Raft, and Redis.
Why Join Stream?
* High scale/ difficult engineering, we have customers using our products with millions of users
* Default alive. Startup growth opportunity with healthy revenue
* All managers are hands-on and capable engineers
* Edge network of servers around the world
* Great opportunity to learn and grow
Remote: our roles are primarily NL, US, or CA-based (hybrid), but exemptions for remote work within the EU may apply to specific cases.
Maybe in specific fields this is true, but a lot of folks in Big Tech view open source as where developers who couldn't hack the interviews end up (they also hold a pretty similar view of startup engineers, unless they are ex-FAANG)
Location: Germany (UTC +1/+2), EU citizen
Remote: preferred
Willing to relocate: possibly
Technologies: C# and previously C++ and Java, prefer functional style and privately dabble with F# and Haskell. I know SQL, Azure, Docker, high performance computing (Monte Carlo simulations), see also CV
CV: https://stash.ldr.name/wwtbh/rcv-202509-b28e.pdf
Email: whoshiring-b28e /-\T ldr D()T name
I work in mathematical finance so a lot of domain knowledge in that area (derivatives, pricing, probability theory).
Quarkus is just a little too much like magic for me. Too many annotations hides what's going on underneath, which makes me feel a bit uncomfortable. But I'll accept that's probably just me.
Vertx on the other hand, which it is built on and which itself builds on Netty, is excellent, and very performant for typical backend services. It now has support for virtual threads too.
Alternate browser engines are now possible in the EU, there is just not much interest in porting to iOS. To me it sounds just bad UX that the first thing you need to do on Chrome to enable Adblock is to switch browser, vs. just installing an extension with the default browser that probably 90%+ of Android users use.
Anyone who is running back-end code in Next.js has no idea what they are doing. It could be acceptable if it is a toy project and you want to get something quickly but even for a small operation or MVP, the whole thing is not coherent.
I've wrote previously about nextjs: https://omarabid.com/nextjs-vercel My opinion remains the same: Most of the issues in Nextjs are not a bug but a feature. A feature that only functions and locks you in Vercel platform.
Since their routing/SEO/content features are also now less functional, there is really very little reason to use Nextjs especially with React Server Components.
> If I'm writing a document for human consumption then why would I expect the dates to be sortable by a naive string sorting algorithm?
If you're naming a document for human consumption, having the files sorted by date easily without relying on modification date (which is changed by fixing a typo/etc...) is pretty neat
Have you ever wondered if your biggest limitation is the very thing you’re certain about?
We’re used to searching for answers where everyone else looks, but what if the real solution is hidden exactly where no one dares to think? The world isn’t shaped by physics or formulas alone, but by the way we choose to see them. So next time something feels “impossible,” ask yourself; impossible for whom? For me… or for a mind that hasn’t yet dared to try a different angle?
One of them is that means tested benefits are harmful, and I think it's a really strong one.
But another very common defense of UBI is that mass unemployment is inevitable, but because of technological developments that cause wide abundance, so UBI can be used to make that abundance available to the newly unemployed.
The harms of means testing are many. They include:
- Massive organizational overhead to do the means testing, have appeals process, have fraud detection, and fraud punishment.
- Personal overhead on those who have to 'pass' the means-testing. This can be non-trivial procedurally, and appeals tend to be very complicated. Moreover, the consequences of making a mistake that gets marked as fraudulent are severe.
This makes it quite time- and stress-costly to get these benefits, and makes some people skip them.
- It creates weird economic incentives, if done exceptionally poorly, it creates situations where an increase in net income causes a decrease in gross income. In other situations you get an effective marginal tax rate of nearly 100%, which discourages work and prevents the building of wealth by advancing a career.
That is completely untrue. Companies frequently own their own stock, and issue more when the price is high it continues to be quite valuable to the company
SEEKING WORK | Remote | Lead Infrastructure Engineer
I am a Lead Infrastructure Engineer with 20+ years of experience.
Whether your team is stuck troubleshooting infra issues, needs extra hands on an infra-heavy project or is just lacking tech leadership on the DevOps topics, contact me and we'll figure it out.
I prefer to work along the existing engineering teams, mentoring or training them while working together on the real tasks. This is a very effective and also a flexible way to learn and as a bonus, some work gets done on the way.
I am located in EU (Estonia) and work remotely with occasional on-site visits.
The usual topics are various AWS services, Elastic Stack, Linux, wide range of troubleshooting, infrastructure as code, logging & monitoring, managing cloud costs, but I find it rewarding to venture into new areas together with the team.
There is a lack of proof that the developer is linked to a sanctioned entity. Not saying it isn't, but The Verge should be at least trying to verify that IMHO (instead of taking the statement at face value); I'd even trust a "we verified it but won't publish to protect the developer".
You say it's purposeful, they say it's incidental. Israel still supplies Gaza with water, albeit at a substantially reduced rate. Roughly 40% of the water infrastructure remains operational[1]. Therefore, your maximalist claim of "destroying all life supporting infrastructure" is false.
Russia has hit plenty of life-supporting infrastructure in the affected areas of Ukraine and millions have been displaced. Will you therefore admit a genocide committed by Russia?
APIs are the backbone of modern apps, but weak security can expose sensitive data and invite cyberattacks. API pentesting helps fix this by simulating real-world threats to uncover flaws in authentication, authorization, input validation, and business logic.
Key benefits include:
Protecting sensitive data from breaches
Ensuring compliance with GDPR, HIPAA, PCI-DSS, and more
Preventing business logic exploits and revenue loss
Strengthening authentication & access controls
Reducing financial/operational risks
Building customer trust and safeguarding brand reputation
In short, API pentesting strengthens your overall security posture, keeps systems resilient, and protects both your business and customers.
* You're not just a growth marketer. You’re a full-stack creative operator.
* You’ve probably done things like:
* Run playbooks that didn’t exist yet
* Gotten products featured on Times Square billboards and Reddit threads
* Built shareable mini-tools that turned into full-on acquisition channels
* Sent physical mailers that turned into million-dollar pipeline
* Landed your company on 10+ podcasts in a quarter
* Have taken a product from 0–1m+ MAUs or scaled growth to $5m–$20m ARR
* Built acquisition loops from scratch
* Know how to make technical content go viral
* Are a creative thinker with deep operational range
* Can juggle many ideas, experiments, and channels at once
But I do believe we'll get to the point they will replace more and more engineers. yes, I don't know how fast, I don't know if LLM will be able to reach that point. But eventually, all that money in research will get somewhere I believe.