How do you use it? I explored building on this as a platform but ditched it because only crypto nerds seem to use it and fiat is used all around anyway.
or efficiency is more important because you have a high load of people you need to interact with. I was a grammer nazi back in the day but stopped caring because the ROI is minimal and I've got shit to do that's more important. so maybe it's the same for them
I've never understood the "efficiency / ROI" argument. What is the "Investment"? What's the time delta between using the shift key and not using the shift key? Does it even add up to one second per year? What's the accumulated time loss from spelling "grammar" properly?
If the delta is simply "cognitive load" then we're back to the theory I already posted.
I'm not certain about shift deltas, but one typically can type faster at the cost of increased errors. I type quite a bit, so even small percentage decreases in total time spent typing is significant. Humins ar rpretty gdood att standing under even very mxed and grbled txt.
The price is often paid by their subordinates, and ultimately the business. I remember working under a pretty inarticulate "senior leader", and he'd send these 3-word barely understandable E-mails to his directs asking them to do something. There would be a frantic scramble of meetings and discussions trying to understand what it is he actually wanted us to do, with a lot of guesswork and arguing. Nobody wanted to tell the guy he was as understandable as a pigeon, so we usually just guessed. Sometimes guessing very wrong and wasting an enormous amount of resources.
They're willing to boil the oceans to write better emails and, alternately, not have to read emails others have sent. So I don't think it's a lack of desire. I suspect it's more atrophying of ability to put effort into anything.
By your logic, you didn't put in much effort into your message. Besides not capitalizing the first letter of every sentence, everything else looks great though for me, and I'd imagine it was low effort for you. Those messages between billionaire read like the worst texts from low IQ teenagers.
I think you're right. Only people trying to look up care about appearances, a millionaire CEO will reply with "sounds good - Sent From Outlook for Iphone", while the intern will write a full thesis level reply on why they need pto.
In this case, sure... that said, I've worked on a few sites where more than half the traffic was bots because the content was useful for other sites (classic car classifieds/sales site). The fact that just over half the page requests were actually search query results is what meant a lot of optimization steps in practice... Implementing a "search" database (mongodb and elastic were pretty new at the time), denormalizing a lot of the data structures on the "enterprise" SQL structures for search and display for not logged in users, etc. Heavier caching, donut caching, etc.
It was an interesting and sometimes fun part of my career. Working on a site/application that isn't necessarily a tech site, and that I have a personal interest in was pretty great... some of the pace for sales/commercial features less so, with sales making deals requiring deep integrations on impossible timelines. You learn a lot when a self-hosted site is being kicked while it's down... The cloud migration to get a better use of flexible resources, etc.
That's too funny. If true, really looking forward to the Cloudflare response here. I'm unsure how you would spin that in a way that didn't seem self-serving.
It's very clearly disclosed in the linked docs already, it says that Cloudflare Bot Protection will block it same as all other bots, unless you choose to allow it as an exception. If they didn't do it that way, people would accuse them of either bypassing their own product (possibly anticompetitive) or just having a low quality one.
So it doesn't take any action to work around other bot protections? Feels like that would be on the list of features an AI company wanting to scrape would ask for.
Cloudflare crawl respects robots.txt. It does not attempt to bypass any anti-crawling measures. If the site doesn't want to be crawled -- whether it uses Cloudflare or not -- this product will not help you crawl it.
Some sites actually want crawlers -- e.g. sites that are selling a product, documentation, etc. That's what this product is meant for.
Is this just a way to strong-arm non-cloudflarians into adopting their platform if you don't want your site crawled? It does sound like they are selling the solution to avoid their own content crawler.
fuck firecrawl. they copied my idea by showing interest in my product and then copied it, used their YC money to give it all out for free. fuck nick in particular. I'm still salty over this
"they copied my idea by showing interest in my product and then copied it". What exactly is revolutionary about Firecrawl or your product? Scraping APIs have been around for over a decade.
I was the first to return markdown and use reader mode stuff to strip irrelevant stuff. Theres copying and there's talking to the founder sounding interested to have your team copy what I did in the background. One is fair game, the other is a dick head move.
I think that is a neat idea and it sucks this happened, but how long before somebody simply saw that feature and replicated it? I'm curious, had you considered a deeper moat than that?
This is especially relevant given AI is making this kind of thing easy at an industrial scale. I think we should all be looking for alternative moats.
Sometimes timing is your moat and that's all you need. That being said I'll probably start limiting my public releases to revolve around standards I want implemented.
I'm rethinking the sources of value moats are built around. It seems like the landscape is changing and dimensions such as location, perspective, experience, and attention weigh more than they used to.
> but how long before somebody simply saw that feature and replicated it?
This is a good example. The, idk, "value store" of your org just switched from products and services to the employees who understand your process from a couple angles and can write well.
To partially clarify: "Idiot proof" is a broad concept that here refers specifically to abstraction layers, more or less (e.g. a UI framework is a little "idiot proof"; a WYSIWYG builder is more "idiot proof"). With AI, it's complicated, but bad leadership is over-interpreting the "idiot proof" aspects of it. It's a phrase, not an insult to users of these tools.
Which would be a good idea, as a European. I'd hate to see the investment go to waste on taxes that are spent on stupid shit anyway. Should go into R&D not fighting bureaucracy.
I just launched bookcall.io publicly last week. Think calendly that treats your scheduling page more like a sales funnel. Very important if one call can make you a bunch of money. Page builder, brand assets, videos, documents etc. attachable. Forms, video calls, everything included.
Also launching a supabase security scanner. If someone wants a free scan hit me up. Includes POCs and verification before and after remidiation. Goodbye false positives.
I've been working on that for a client since yesterday (as a fractional CTO). Pretty hectic, basically nothing really works and we don't know yet if all data is lost or if anything is recoverable or when AWS UAE will become functional again so we can recover that region.
Finally, I have a very good argument for multi-region deployments ;))
We didn't do multi-region deployments, but we did store database backups in a separate region just in case something really bad happened and our AWS region became unavailable. Also had a plan/some ready Terraform stuff in order to start setting up a deployment if it became apparent that the region wasn't coming back anytime soon.
IMO, if you're using AWS and not replicating your data somewhere else, this should be an eye-opener for you.
Not sure why everyone read this as me doing anything here, I'm a fractional CTO, which is kind of an advisor. Nothing invaluable will be lost tho. It's not the core platform, just a localized version for specific customers in the region.
To a lot of managers/startup execs this is something like "we won't ever need this". And I'd agree to some extent for not so important/rebuildable services. Depends on what you need. In startups, you don't have infinite time you can spend on stuff. But this makes a good case: if a geographical region only has one AWS region, don't keep data or run services that can't be easily rebuild somewhere else.
In europe you can just pick two AWS regions and you stay in the same regions, UAE not so much.
There’s a reason literally every enterprise of any size in the early 00s not only had a DR site, but a DR plan they would test multiple times per year.
1. Just having a copy in two places doesn’t mean the copies are both good or that you can get DR online in any reasonable amount of time.
2. You quickly figure out all the things you thought “weren’t important” that prevent you from actually doing a successful DR test.
They amount of things that “cloud first” people just assume naturally takes care of itself because it’s in the cloud always amuses me.
You should have that for your main data, yes. I insist on that as well. Making backups, cold storage, and getting them back online. Yearly is not enough. My point was that not everything needs a backup or a DR. Spend your time wisely, we're talking startups, not enterprise. Can't talk more specifics obviously
The fact half the internet was down the last time US east was down tells me it’s not just startups that foolishly think they don’t need actively tested dr copies and plans when they move to the cloud.
That was my point: now we have a very specific case we can argue. I always used the "what if a plane crashes into the data center" argument. Now I can say: in one of my engagements, we lost a datacenter completely because of a drone attack. That's a first for AWS as well, but we can draw from reality, not hypotheticals.
Of course, no worries. Nothing irreplaceable will be lost ;) It was meant as a general example to be used in future arguments for everybody in tech leadership.
reply