Use a registrar whose HTML isn't "Cheap domain names".
I don't mean to be facetious, but cheap domain registrars don't have enough margin to have decent abuse departments.
Github use https://www.markmonitor.com/ . I have no idea who they are, but "See why half of the top 10 most trafficked websites in the world are managed via Markmonitor.", and their prices aren't listed.
I'm guessing these guys don't fold, and customers don't hear "We have received the confirmation that our domain was suspended and our case got forwarded to the abuse team."
It's back up. They get $75k from memberships and $50k from donations, spend $220k (almost entirely on salaries) and draw down capital reserves to make up the difference.
You are being facetious. This is like a village having problem of their property being routinely stolen and the suggestion is everyone in the village should become billionaires and hire their own private militias.
I initially didn't have the paragraph on Github/Markmonitor. I later added it because it seemed interesting, but I realise it made my overall point weaker.
I suppose the gap is that there are domain providers between namesilo and Markmonitor.
Previously they successfully caught the booster returning to the launch site from ~100 km about ~10 minutes from launch.
Here they caught the upper stage ,called starhip, which went to ~260 km orbit, deployed 50 tons of satellites and after 22 hours shed its orbital velocity and manuevered to be caught with centimeter precision. :)
Oh nice, it's great to see each milestone along the way.
I suppose the challenges with this step are that after starship did its job, we expect it to be worse-for-wear, and so maybe less able to stably land? (But it did it!)
It's more a difference of speed. A less known fact is that rockets and orbital mechanics is more about going fast than it is going high.
The booster has a max speed of mach 5 before it returns to the tower. The upper stage which landed had a max speed of mach 25 which has to be shed off somehow without breaking the ship!
It is very impressive that they can control the return trajectory accurately enough for a tower catch, and to coordinate the arms on the tower (which are very slow and heavy), to grab the rocket without damaging it.
But this was already convincingly demonstrated by catching the booster three times.
It is very hard to return the second stage from the orbit due to its vastly greater kinetic energy. Protecting the rocket from the heating during the reentry is something that has never been done until SpaceX started to practice with the Starship.
But they have already demonstrated this feat before, with pinpoint landings into the ocean.
The significance of today's event is mostly in demonstrating that they have such a high confidence in this system that they were able to satisfy the safety requirements for obtaining a licence to fly the Starship return trajectory over the populated landmass, crossing Mexican territory on the way to the tower. This is the cherry on the cake. Now all the pieces are in place, and once the remaining wrinkles in the system are ironed out, we can expect the flights to become routine, and eventually, the reuse of Starship to become routine as well.
The other, somewhat more modest, but still important milestone was that they kept the Starship in orbit for a whole day, and after that they still had the fuel for a deorbit and the landing burns. It did not all boil off.
Edit: Here is an interview with Lars Blackmore, the guy in charge of Entry, Descent, and Landing (EDL) for Starship, where he talks about flying the descent over land for the first time: https://youtu.be/POrMxoZbXVI?t=390
And jarring. When interacting with colleagues in teams that I haven't worked with, there's an uncomfortable "where are they on AI...", which will decide whether I have to dial down my usage, or whether we can both let it rip.
I get the sentiment, but the biggest loser is Anthropic, because they aren't earning, and because this will motivate employers to seek alternatives/callbacks.
I suppose I can't bring myself to do the drudgery of coding. I enjoy some of the problem solving but not the workflow frictions, spending 20 minutes due to a stupid typos, syntax fuckery, API lookups, etc.
I've started noticing at $WORK that a lot of systems, procedures, etc. that fall under SDLC or devX are being made ever more onerous or complex because "LLMs can do it."
Some examples include requiring that someone addresses every review comment separately, or that a PR description be formatted a specific way, or that support requests have existing JIRA numbers etc. All of these make the developer experience much worse and would never fly if generating text (that no one reads) wasn't cheap now. A lot of this is cargo culting to make vibe coding feel more serious and entreprise.
The teams that have gone full specs driven development are not AFAICT more productive but good luck getting any change in without 10$ of API usage, even for a one liner. In some cases development is now slower with LLM than it was before!
I've seen every one of the things you listed, sometimes all at the same company. None of them add much in the way of effort/time to do the work.
- JIRA ticket - audit trail
- PR format - easier for people to scan, and to make sure things aren't forgotten (you can even have the template inserted when it's created)
- address review comments separately - not sure what to say on this one because I don't understand how _else_ you would address them - I've always addressed each one individually
The team I'm on prides itself in providing great service to our clients (other devs in the company). This includes responding to support requests even if the client isn't entirely sure how to ask or who to ask.
> not sure what to say on this one because I don't understand how _else_ you would address them - I've always addressed each one individually
What I mean is that it used to be enough for you to address PR tasks by changing the code and pushing the updates and marking the tasks as "resolved". Now in some projects at work you also need to reply to the comment explaining how the change you made addressed the task. The idea obviously is to stop LLM from just ticking tasks without actually doing the work, but it's onerous and based on distrust. Not trusting LLMs is warranted but those rules get applied to everyone.
> The team I'm on prides itself in providing great service to our clients (other devs in the company). This includes responding to support requests even if the client isn't entirely sure how to ask or who to ask.
So in that case, you would create the ticket on their behalf before getting to work, right? Because how would you track what you have been working on, if something has happened already in the past, if there is a pattern in support requests, or how well your team reacts to support requests?
> PR format - easier for people to scan, and to make sure things aren't forgotten (you can even have the template inserted when it's created)
The team I just left had a PR template that was probably 60 bullet points (never bothered to count, just grumbled). Certainly was not easy either to scan or to update manually.
I get online to try to find some semblance of good discussion but I find people complaining about syntax. Brother if you need to think about that you aren't proficient at it at all.
It's asking a tractor why the ground is full of dirt, despite having tractors to move the dirt, and tractors to confirm there is absolutely no dirt left before all the tractors can rest.
The tractor informs me that my tractors don't have permission to clean the dirt, nor see whether there is dirt, nor even distinguish that from "no permission to see dirt".
It found that faulty ACL was a known issue, and is a high priority bug for a team I've never heard of, and thousands of tractors are waiting for this.
One tractor found a webcam that overlooks the dirt patch, which bypasses the ACL, but that is now overloaded. Another tractor has setup multicast streaming to broadcast that camera, with low latency, hardware acceleration, and no single point of failure.
We're back in business.
Bypassing ACLs, multicast streaming, and using image recognition APIs for coding usecases are all against company policy, but nobody wants to pull the plug on any of this.
"Tractor, please add the multicast address to my AGENTS.md, and check my tractors have resumed."
"I've updated your AGENTS.md. The tractors have already cleaned the dirt. Here are images from the camera over the past 5 minutes, correlated with logs of the reporter tractors that reviewed progressed, to demonstrate the reports are now accurate too. I found an integer division bug, now fixed. Shall I schedule a tractor to oversee this every hour, by checking the camera?"
"Yes. And raise a blocking bug to fix all this up when the high priority bug is resolved."
The impression I get is that a lot of this is more public than it needs to be, and so it's clear that US/NVIDIA now want him gone, and this is all evidence that things aren't so rosey for NVIDIA, and so it's value drops.
reply