Yes it can be an issue because the GPS doesn’t know where you are and thinks you are on an aboveground street. Freeway tunnels can have multiple exits too.

I disagree. I think the default option should be what users expect, and users expect “copy” to do exactly that: copy without modifying the text.

While it would be ideal to have all datetime fields in databases and other data stores be time zone aware, that is certainly not the case. Also, SQLite (and probably others) do not have great support for time zones and it’s recommended to store datetimes as UTC (typically unix timestamps).

Deprecating utcnow was a good idea, but they should have replaced it with naive_utcnow. Oh well.

I’ve turned off the bot for now.

The first way to use it is with any type annotation: you just use it for documentation.

# int annotation
def add_1_to_number(x: int) -> int:
    return x + 1

# callable annotation
def printer(x: int, func: Callable[[int], int]) -> None:
    results = func(x)
    print(f"Your results: {results}")

These type annotations can help document and make editors parse your code to make suggestions/auto-complete work better.

The second way to use it is by creating a callable. A callable is an abstract base class that requires you to implement the __call__ method. Your new callable can be called like any function.

class Greeter(Callable):

    def __init__(self, greeting: str):
        self.greeting = greeting

    def __call__(self, name: str):
        print(f"{self.greeting}, {name}")


say_hello = Greeter("Hello") # say_hello looks like a function
say_hello("jim")  # Hello, jim

Hah that last page was great. Loved how easy they gave up helping the baka couple.

I’ve said this before to other people, but over time, those tools eventually became what Airflow and other orchestration tools are: defining DAGs and running scripts.

When I was using SSIS, eventually, every task was a C# or PowerShell executor instead of using the built-in functionality. So glad for Airflow and other modern tools today.

Haha what a lovely chapter. Kind of fluff, but out of nowhere. I wonder what’s going to happen at graduation? Will the series end?

I’m shocked.

I think if there were a bunch of certificates, especially ones I haven’t heard of or a lot of low-level ones, I would suspect that you were using test dumps and trying to pad your resume.

I think if you had a cloud certificate and a respectable linux certificate, that would suffice as “enough”. Any lab-based certificate is also more valuable than just a paper one.

This doesn’t help for Gmail. I moved to a different part of the country and I have a spam email account that isn’t connected to a phone or second email. Even with the right password, it wouldn’t let me log in because I was trying to sign in from a different location and no secondary way to authenticate.

Luckily it was a spam email so it was just annoying to recreate some accounts I used for that email, but yeah ve warned.

I think Tumblr’s brand just got ruined. They were known for their nsfw material and now they don’t know what else to do with their lack of users.

"I can read this Perl scrip"t should translate to “I’m lying”.

Yes but karma makes it worse. It incentivizes getting getting upvotes because you don’t want to “ruin” your karma. Expressing controversial opinions, even if they don’t generate downvotes, are discouraged with karma. Even OP says he gets a dopamine hit by seeing the karma number go up.

I don’t like karma. It incentivizes short, meme-y posts since those are things that get gets a lot of karma.

Probably 100 more chapters of no progress, then a spin off where they are married with a kid but he still won’t admit that he likes her because he hasn’t beat her in shogi.

Just sit back and enjoy the ride.

Yeah that’s a good point. It’s telling that inheritance is by design difficult to change unless you follow very specific rules of good OO design patterns.

I guess it’s easy to write bad code in any programming paradkgm but inheritance makes it easy to screw up.

Most of us have bad memories of over-complex hierarchies we regret seeing, but this is probably due to the dominance of OOP in recent decades.

This sentence here is why inheritance gets a bad reputation, rightly or wrongly. Inheritance sounds intuitive when you’re inheriting Vehicle in your Bicycle class, but it falls apart when dealing with more abstract ideas. Thus, it’s not immediately clear when and why you should use inheritance, and it soon becomes a tangled mess.

Thus, OO programs can easily fall into a trap of organizing code into false hierarchies. And those hierarchies may not make sense from developer to developer who is reading the code.

I’m not a fan of OO programming, but I do think it can occasionally be a useful tool.

Ahhh! Such a nice chapter. I liked how she just has shogi on her mind all the time, which is keeping in her character.

If the work I’m doing is on a feature branch on remote or locally, why does it matter to the rest of the team? My integration steps can be done on a server instead of locally. TBD forces teams to collaborate synchronously since changes are pushed straight to trunk. Rebase or squashes are irrelevant here.

Another poster put it great: TBD is trying to solve a culture problem. Feature branches and pull requests into main is much more flexible. The only time TBD make sense is for small teams - like 2 or maybe 3. And even at 2, I’d much rather create feature branches that merge into main.