neya

I was talking to someone about a possible clutch issue on their car and they pinpointed to with a screenshot saying my diagnosis was wrong. I've been a car guy all my life and so I am not some amateur. I just wished them good luck and went about my business.

6 hours later guess who is stranded in the middle of the road? Not me.

It's an eye opener. Think about it - today, it was a mistake. But, what if it really happened? What if you really lost access to all your years of hard work? It's a wake up call. A blessing in disguise to store what matters to you the most locally, backed up offline. Never trust any single provider. Be it MS or Google or Apple. RAID is the way.

Same here. I have a personal mind frame of:

    "If you have the option to work on something you like on your computer or just even glance outside into the sun for a moment, always choose the latter."

This golden rule has given me more benefits - including finishing the task way faster I would have taken longer if I just sat in front of the computer.

They also had a browser called Orion and till date that gave me anxiety because YouTube videos won't play the first time you load them, you need to refresh the page (randomly) and similar other weird quirks. It's state hasn't changed much over the last year either, so I switched back to Brave now.

Once in a while someone recommends Kagi and I do go check it out. However, the index size is very small. It depends a lot on what you search but for most of my searches, it is not enough. I feel duckduckgo and bing together are a perfect replacement instead.

This is the best news ever. Been building with Claude Code + Deepseek and it has blown me away. $10 gets me ENTIRE PROJECTs. Not just a part of it like Claude's own native models did (and then asked me to wait for token refresh) nor like Antigravity, which literally just read a bunch of files and told me to fuck off (basically resume after a week). Atleast it gave me an implementation_plan.md.

OF course I understand this won't be "permanent" permanent. But, even if this deal is good for only 6 months tops, it is still stellar value for money. $10 a month to automate bulk of my grunt work? That's insane.

They probably slogged to death before this and finally are recouping what they were owed over their lifetime if you put things into perspective. I feel happy for them and hope they use it wisely and actually retire.

Just saying either way is possible unless both sides of the story are out in the open. You seem to start from a point of view of malice, I'm simply suggesting possible alternatives.

Or they fixed the issue to remain compliant so GCP would restore access. Again, I know it's fashionable to hate on Google here, but there are always 2 sides to every story.

> Whatever the account manager said didn't inspire confidence that this wouldn't happen again.

Or..they couldn't remain compliant with one of the strictest cloud vendors' policies.

This is just typical anti-Google FUD. Been on GCP for nearly a decade and as do my peers. Sure, you hear about a few stories like these and in this particular case with Railway, I would actually wait to see what caused the trigger for the suspension - both from Railway and from GCP. But, this sort of thing happens with every cloud provider including AWS (you can google for the same thing "AWS shut down our account with no warning") and you'll find tons of stories like these.

As a former GCP consultant, I can share that these sort of shut downs aren't random and it's usually due to the customer not being compliant - that breaks cloud compliance requirements for the big clouds, so automated systems flag it. Eg. Someone serving CP on their CDN, for instance.

The Railway incident report also doesn't directly address this at all other than:

    May 19, 22:22 UTC - P0 ticket filed with Google Cloud. Railway's GCP account manager engaged directly.

So, I would actually like to know more (What did the account manager say exactly?) before I just simply jump onto the Google hate train because it's cool to do so.

Top comments as usual are buried in deep hate for Google, I doubt that will pressure anyone at Railway to address this.

This has significant consequences for companies hosting their private repos with GitHub. It's a huge security threat if the attacked has access to the source code. At the very least, GitHub should let people know if their repo was part of the hack or not. It's the most responsible thing to do.

The actual source is a video of the said Apple engineer from their TikTok account:

https://www.tiktok.com/@honeycoolcat/video/76247432319971361...

In my personal experience, this is definitely the case. My iPhone 14 Pro Max slowed down a LOT exactly 3 days before the launch of the new iPhone. I thought it was just a coincidence and did upgrade to 15 and it happened again. Someone on reddit a while ago actually graphed Google trends data for "iPhone slow" and found out there were peaks for the search term right around Apple's launches.

The other day, I saw a clone of OpenRouter pitched as a "superior" alternative simply because they were "European" only to find out their entire stack was dependent on Cloudflare. That's why I'm always sceptical of providers who claim superiority just because they want to "escape" US control because that's rarely the case.

So, we're just going a full circle back now. Interesting.

Hey, thanks for responding! I was just pointing out to the parent comment that going by a programming language to judge app quality is a very relative metric, so I just used Elixir to help them understand. Thanks again for your hard work on the project!

Nope. On the internet, I don't owe anyone anything, especially to someone who created a new account just to argue. Do your own research. And using your real account will elicit better quality responses. Please try it.

Here's something better than that:

https://github.com/plausible/analytics

Elixir.

> No one is doing that, these people don't exist.

"I don't personally know enough people doing what a mega-corporation with a massive market research team with multiple layers of market research audits has concluded people claims to want, so I'm just going to diss the product"

We are going to be seeing a lot of these moving forward. It's the easy way out. If you've worked with Google, you will know that it's an environment where accountability doesn't thrive. You will find people who know nothing about Google's product portfolio hold advisory roles around the products. They don't care, there's no one to even question them. They just know to make colourful graphs with the most useless metrics to justify they "add value" to the company. Expecting them to take accountability is like trying to mix oil and water.

> It's additional software that many users didn't ask for, don't want and will not be aware of

You mean like Siri? It does the exact same thing and no one asked for it, either. That shit barely works too.

What you are describing is a the role of a manager, not a software engineer. Software engineering has very little to do with writing code, but more on architecting at the higher level on what needs to be done. The code is just the executional part. LLMs can code? Ok good. Without a clear architectural pathway / direction, that code is just useless. It's not tech debt. It's just a bunch of random strings. You can argue that Claude code and others do create a plan of attack - but still, it's not at the architectural level, but rather executional level.

To me, architecture starts all the way from the top - even before you write a single line of code, you do the DDD (Domain-Driven Design) and then create a set of rulesets (eg. use the domain name as table prefix) and contexts and then define the functionality w.r.t to that architecture. LLMs can do all this - only if you ask them to explicitly. So, they are pretty useful to brainstorm with, but not autonomously design reliably and push it to production with your eyes closed and support a 100,000 user base. It's a far cry from that.

But sure, you can upsell to management about the vanity metrics like lines of code and get that promotion with LLM. But, it's still not software engineering.

> People who don't pair caffeine with nicotine simply have no clue what they are missing ;)

We do, and that's called cancer;)

> I’ve always been struck by a recurring trend: whenever a customer throws a tantrum, threatens legal recourse, or takes things to an extreme, they are almost invariably another business owner.

If a business owner threatens legal recourse, then, probably it's them. If multiple business owners threaten legal recourse, it's definitely something you're doing wrong. And that usually is along the lines of over-promising and under-delivering in an agency context.

It's always the MBAs. The organizational structure incentivises them on the wrong metrics. So they adapt and optimize for that. In real life, after a while, you hit a plateau with features and market demand. What these MBA clowns love to do is take what's already perfectly fine and mess it up and create a road map for it to fix something to being it the way it was, so they can justify to their higher ups they are "adding value" to the company. And half way through this, they leave the company. Now some other new employee comes in, has no idea why this had to be reworked and messes it up even more. You have this loop enough times, you end up with how software engineering works in the fortune 500.

The moment you hear "let's circle back" enough in meetings, that's your tell tale sign to quit the workplace infested with MBAs. A good organization is always run by engineers at the top level and engineers don't incentivise engineers simply for working on roadmaps of perfectly fine existing features. That's the difference.

> This idea of software threatening the user with consequences is totally wild and dystopian.

This idea of software built on top of reverse-engineered data threatening the user with consequences is what's really even wild and dystopian.

From what I can see, one of the top comments (at the time of this comment) is worried about legalese claiming to have "non-exclusive, worldwide, royalty-free, fully paid-up, non-sublicensable" access to your source code. I think it is very fair criticism to not want to give away your source code.

https://news.ycombinator.com/item?id=47953501

Haha thx :)))