860 karma · joined March 5, 2025
Some features are annoying to work on, some have long term implications for how much and what type of work will need to be done. Some just don’t fit with what the engineers want to work on. I know which features are going to take endless stakeholder meetings and which aren’t. I know which are going to require overtime and being on-call. I know which are going to kill off my pet project.
The most self-serving action a software engineer who doesn’t want to work more than the bare minimum can take is to reject as much as possible as being too difficult or bad or some other excuse.
Think Figma comments as a service. Examples of it in production: https://www.workcanvas.com/
If you think most engineers are evaluating things based on the value it’ll drive for their product, you’ve lived a lucky career (and long may it continue).
Be willing to temporarily suspend your services in order to prevent the malicious behavior. Do the manual work to allow genuine customers to keep using your service, e.g: require manual account approval. You need to treat every one of these chargeback transactions as a risk to your businesses ability to operate, each that you allow to happen increases the risk of permanent damage to your business.
Reach out to your account manager at PayPal, this is not something that should be going via frontline support. You need to be talking to a person who knows and is responsible for your account. If you don’t have one, get one. If you can’t get one, look for anti payment fraud businesses that work with PayPal, they may be able to get a direct line to PayPal on your behalf.
For the future, if you’re dependent upon a service provider you should always have someone you can reach out to directly. If a provider isn’t willing to offer that, find a different provider. Financial services especially are very risk averse and will jettison your account if they get even a whiff of something untoward, whether you tried to prevent it or not. The cost of recovering from that will dwarf the cost of any drastic mitigation you take now. Losing your PayPal account is worse than turning off purchases for a few days.
“Works on all platforms, no meeting bots Granola transcribes your Mac's audio directly, with no meeting bots joining your call”
Specific to this story: most of the world has instant payments without using blockchains or stablecoins, it’s only the U.S. where the banking system somehow hasn’t realised they can do instant payments using traditional banking technology.
Anyone posting that they’re skeptical about the use cases for blockchains on HN 10 years ago will have the same skepticism now. Nothing has changed.
> It is my opinion that anyone not at least thinking about benefiting from such tools will be left behind.
The read here is: Microsoft is so abuzz with excitement/panic about AI taking all software engineering jobs that Microsoft employees are jumping on board with Microsoft's AI push out of a fear of "being left behind". That's not the confidence inspiring the statement they intended it to be, it's the opposite, it underscores that this isn't the .net team "experimenting to understand the limits of what the tools" but rather the .net team trying to keep their jobs.
"...carried a pre-sale estimate of over $70 million..."
"...the artwork came to the market without a minimum price guarantee from the auction house..."
"Oliver Barker, the evening’s auctioneer, began the bidding for the bust at $59 million. But his bids stalled at $64.25 million. Three minutes passed as he hunched low over the rostrum, hunting for bidders, Nosferatu-like, until announcing that the lot was a pass."
Can someone explain how these things relate? If the pre-sale estimate was $70m, there was no minimum price guarantee (a reserve?) and a bid of $64.25 million (90% of the estimate) why didn't it sell?
The article goes on to say:
"“No one who is an informed buyer who is serious in this market — billionaire or not — is going to pay what essentially amounts to a 50 percent premium on something that sold in recent memory,” said Todd Levin, an adviser in New York."
Someone was willing to pay $64.25 million, a 30% premium on the last sale, $70 million is only 40%. Where does 50% come from? Why is $64.25 million bad but $70 million is good.
Databricks is the antithesis of Neon. Neon is driven by product, Databricks is driven by sales. Opinions of Databricks in a thread about Neon are going to be on the negative side (but not necessarily representative).
Support is typically low paid because it's a lot of effort for little reward, no matter how much you pay someone in support, there's only so much impact they can have on the bottom line. The organization as an organism where every organ is as equally important as the other is a beautiful sentiment but the appendix is getting jettisoned at the first sign of trouble. Support, no matter how valued and important to the organisation it is, is never worth $200k/year on the output of 1 person.
The exception to the rule for sales is the canary in the coal mine: sales measures itself, but every role can (and will) be measured when the pressure is on, there will be competition for budget, and the support team will get squeezed until they're empty while the engineers coast. I would be more convinced that this model could survive outside of the vc bubble if sales had bought in to too. Sales as a competitive sport is cultural, not fundamental.
Anyway, not criticism, just musing, love that they're trying it, even if this doesn't work out, everyone had a few good years, it's worth a shot.
I completely agree but I think that's a very hard sell. People who write code are often years deep in their preferred workflows and asking them to reconsider how they build things is a very big ask.
> Even if developers prefer textual code when on their own, when they're working with non-developers (product teams, clients etc) there's a big benefit for being able to share and present how things work.
The problem here is that developers lead implementation. The ideal implementation for a stakeholder is rarely the implementation that is delivered, because developers are taking requirements and translating them into the things they want to build. That's why so many products end up bad: developers have too much power by virtue of code being seen as some sort of magic spell that only a true genius can master. Can you imagine a non-technical person successfully dictating that the solution must be built with visual programming?
Low code / no code is powerful because it turns the relationship between product owner and developer on its head, it puts the product owner back in the driving seat (instead of a passenger begging the developer to go in the desired direction and accepting they'll probably end up somewhere... nearby, hopefully). Hiring the wrong developer(s) can be very bad for a company because of how much a developers choice's influence the product and business.
The proliferation of low code / no code in business often comes from outside engineering, many developers, regrettably, love to write code. Often you'll find that non-technical departments of companies have secretly started using things like Make and Zapier and n8n without telling the engineering department because they feel like they finally have the opportunity to make technology work for them.
Developers that exist in service of product are already using platforms like Make and Zapier and n8n because they understand how much value there is in programming without writing code, but for them visual programming probably isn't that much of a differentiator because they already have a vision in their head of how programming works.
Anyway, your product is great, I am sure you'll succeed regardless of the approach you take :)
* Flowcode is a clever name but since you are positioning yourself as an alternative to code ("Code is messy and complex") the name is contradictory, just call it "Flow" (or "flows" or "Flower" something)
* You are replacing the legacy of code with something new, embrace new ideas that get out of the "one running process" paradigm, e.g: durable functions. There are a bunch of companies in the space (inngest, DBOS, trigger.dev) who are doing very interesting things, copy/steal/leverage all the great things they're doing -- your product's value is the visual programming
* Most developers today are already writing code so getting out of their code flow to do something visual might not fit well, whereas there are lots of non-developers who would love a product like this (see: the success of Make.com, Zapier etc.) because you're offering the AI integration for creating workflows which gives them confidence to go beyond what Make, Zapier etc. offer
If I were marketing this product, my pitch would be reframing programming as something anyone can do when it doesn't involve code, i.e:: your users can become a developer without writing code, AI-assisted visual programming builds production-ready systems without a single line of code. Code is archaic, (visual) programming is the future. Vibe coding is faster horses, AI-assisted visual programming is flying cars.
LLM-enabled Zapier or Make or n8n is the future, not everyone churning out Claude-written NextJS app after NextJS app.
Almost everything I've seen achieved with vibe coding so far has been long since achievable with low / no code platforms. There is a great deal of value in the freedom that vibe coding gives (and for that reason, I am in favor of it) but the missing piece of this criticism of the criticism is that vibe coding is not the only way to write these simple scripts and it is the least reliable way.
Vibe coding as the future is an uninspired vision of the future. The future is less code, not more.
"The company must change its mindset and become proactive in its approach to compliance. I have decided this can best be achieved by the imposition of a sanction that will serve as a deterrent to future non-compliant conduct by Star and other pub-owning businesses."
https://www.gov.uk/government/news/heineken-pub-company-fine...
Today, hundreds of millions of requests per second can be handled by L4 systems like Google Cloud and Cloudflare. Today traffic to a subdomain is almost certainly being routed through the same infrastructure anyway so there is no benefit to using a subdomain. That's why I describe subdomains as archaic in the context of building a highly available system like Google's.
If you're Google in 2010, maps.google.com is a necessity. If you're Google in 2025, maps.google.com is a choice. Subdomains are great for many reasons but are no longer a necessity for high availability.