If you read Clean Code and other similar books, they don't necessarily advise moving the sub-functions to other files, or splitting them arbitrarily. They simply have the top function delegate to sub-functions that are lower in the same file. Even better if these sub-functions can be marked as private in your language (to avoid polluting the public API of your object). And here the goal is to use function names to document what each block of code (sub-function) does.

Example:

    def process_order(order):
        _validate(order)
        _reserve(order)
        _charge(order)
        _confirm(order)
    
    def _validate(order):
        ...
    
    def _reserve(order):
        ...

Link no longer works. Article was moved to: https://www.joanwestenberg.com/p/smart-people-don-t-chase-go...

Previously, if you had a BigQuery external table on top of GCS files, and those files had Nearline / Coldline / Archive storage classes (e.g. due to a bucket lifecycle policy), you were not billed for retrieval fees when reading those files through the BQ external table.

This was a billing bug that was already mentioned in 2020 on StackOverflow.

But the bug has been fixed on February 21, 2025. So we are now billed for that. We started seeing 10.000 $ of retrieval fees due to that. I did a deep dive and found this.

The fact that some of our DBT projects were re-creating the external tables daily was not helping...

New Zealand startup Montoux shut down after a lawsuit from $46B fintech giant FIS, which accused it of stealing trade secrets—claims Montoux denied. The company had gained traction as an alternative to FIS’s Prophet software, but instead of competing, FIS sued.

Filed in Delaware, the lawsuit alleged Montoux used FIS code and trained AI on proprietary data. With legal costs hitting $600K upfront, Montoux couldn't afford to fight and liquidated. This "lawfare" tactic highlights how corporations use litigation to stifle competition, raising serious questions about monopolistic practices and the barriers to innovation.

> With legal costs hitting $600K upfront

On the one hand, the US legal system is shockingly corrupt and openly pay-to-play.

On the other, if you can't raise $600k -- or $2M -- for a legal defense, you're not really a "promising AI startup." You're something more akin to a garage project.

The smart move for a small company (assuming they don't want to fold) would be to hire an out-of-work lawyer as "part-time in-house counsel" and have them start fighting the case on your company's behalf. File an aggressive response, a motion to dismiss, etc. That way, you've got a fighting chance, and it'll cost >10x less than $600k.

Even with a global lockdown, there will always be a reservoir of virus somewhere.

Some immunocompromised people can carry the virus for weeks.

Also, what about households where one person catches COVID the day before lockdown, incubates for a few days (asymptomatically), then transmits it to another person in the household, who also incubates for a few days...

At the end of the two week lockdowns, some people will still be contagious.

1 Month lockdown, then to travel from anywhere to anywhere you need to stay in isolation for 20 days. I wish this was possible.

Indeed, Jeff talks about it in this 2001 interview : https://youtu.be/p7FgXSoqfnI?t=7m05s

Here is the link to the PDF: https://www.cftc.gov/sites/default/files/filings/orgrules/20...

As a freelancer in Paris, I've been invoicing 625€ daily in 2018 and 2019, and 700€ in 2020, doing Big Data / Scala development with a sprinkle of devops, for the same customer. I think I could get 800-900€ if I find a customer that pays better and focus on the Big Data / GCP sectors. Just need to find a contract through word of mouth, and not through a recruiter that takes a 100-150€ margin...

You get less as a salaried employee in France though...

Having servers offer scp instead of ssh is not the only problem.

What about this part of the article:

Finally, while the danger is remote, it is worth noting that a local file name containing `backticks` (a file named `touch you-lose`, for example) will be handled the same way on the other end; if a user can be convinced to perform a recursive copy of a directory tree containing a file with a malicious name, bad things can happen.

It would be funny if the real Mike Hancoski googles himself and stumbles upon this thread.