1,939 karma · joined January 28, 2013
I actually first heard about it from the Acquired podcast, which is another great example of that same trend.
Only about 5% of the world’s population are native English speakers, but more than twice that number use it daily. For many, AI rewriting isn’t about losing personal style—it’s about making sure they can communicate clearly in a language that isn’t their first.
It’s fair to dislike how AI flattens unique voices, but for a huge part of the world, it’s not erasing personality—it’s making participation possible.
Keeping a human in the loop is essential, in my experience. The AI does the heavy lifting, but we make sure the tests are genuinely useful. That balance helps avoid the trap of churning out “dumb” tests that might look impressive but don’t add real value.
There’s a huge difference between using an LLM to crank out test code and having a product that can actually support complex, evolving setups long-term. A lot of tools work great in demos but don’t hold up for these real-world testing needs.
And yeah, this is even trickier for higher-level tests. Without careful design, it’s way too easy to end up with “dumb” tests that add little real value.
We used to place a can of spam on the tank's gearbox before a long drive, and by the time we reached our destination, the spam was heated up and ready to eat.
DIY only make sense at a very small scale or very large scale, everything in between is usually best offloaded to those which do it as their core competency.
Create a great vendor-agnostic open source tech. Get everyone riled up about the dangers of vendor-locking solutions. Use the new tech to carve yourself a piece of the market from the current incumbent.
It is pretty great and all, but sometimes it is easier to build your app with a simple vendor-locked tech than a super generic agnostic technology.
This way you can simulate the complexity of different devices, geo-locations, and network connectivity levels in your tests.
Disclaimer, I'm one of the founders of Loadmill.
But take into consideration, that non-electric bikes are not very practical commute option during the Israeli summer (for most people).
Public transport (Bus only) is quite ineffective because of congestion.
My analysis of Bird's unit economics in Tel Aviv:
https://twitter.com/ido_co/status/1080883756184023041
</Shameless-plug>
Similar lines could have been written about once crazy ideas that we take for granted today.
It is not exactly like the Uber/Lyft model, but you can think of it as the supply side of the equation, and it does create barriers for entry.
Yeah, our affiliates get a visible iframe to embed in their website, and that is their responsibility to communicate this to their visitors (they can also do it in other ways).
This should work really well blogs and websites who want to avoid ads and look for alternative monetization models.
This way we can offer our affiliates an alternative monetization model. Website owners embed our script, and share the revenue generated from the tests they help to power, while keeping their website free from ads.
But as long as we want to get free quality content, publishers have to see some profit (And I'm ok with that). You opt-in to many things when you visit a website on a regular basis, and tools like peer5 are just one of these things.
(Fixed typo)
Quick question, why did you choose to use a PATCH request and get involved with CORS issues, instead of injecting an image element with a tracking pixel (web beacon)?
You can it here https://github.com/idoco/intergram/blob/master/src/widget/wi...