Just because you can get part of your education remotely or through self-learning didn't mean "anything can be learned online".

And if you were hiring a math tutor for your kid, would you prefer a self-proclaimed expert from watching YouTube videos or would you want someone who got a degree from a credentialed university? And even if you don't care, why are you surprised that others would be skeptical of the YouTube expert?

Remote learning can be fine for some things, and self learning through informal channels are also fine, but it's not a full on replacement for formal education in all cases.

No sorry, that's just fundamentally false. You can't just learn titration techniques from watching a video. You can't learn phlebotomy without an instructor watching you do it to a patient. Hell, you aren't learning how to drive a car from playing a video game.

And I'm not sure where you are pulling the "if you are that powerful" from. You really have an ax to grind don't you.

Ah yes, I'm sure the formal training received by doctors, nurses, lawyers, teachers, and engineers is just an over-hyped "education" that can all be replaced by online MOOCs.

There are real problems with education, especially with the costs, but "anything can be learned online" is the worst take I've heard in a long while.

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

I feel the opposite. We should have mandatory voting for all federal general elections. Treat it like jury duty or taxes - voting is a civic duty. You should be compelled to cast a ballot even if you leave it blank because you have no preference.

Of course, this can only workwith automatic voter registration and 100% mail-in ballots.

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

"I can read this Perl scrip"t should translate to "I'm lying".

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.

Ehhh, I don't quite agree with this. I've done the same thing where I used a timestamp field to replace a boolean. However, they are technically not the same thing. In databases, boolean fields can be nullable so you actually have 3-valued boolean logic: true, false, and null. You can technically only replace a non-nullable field to a timestamp column because you are treating null in timestamp as false.

Two examples:

1. A table of generated documents for employees to sign. There's a field where they need to agree to something, but it's optional. You want to differentiate between employees who agreed, employees who disagreed, and employees who have yet to agree. You can't change the column from is_agreed to agreed_at.

2. Adding a boolean column to an existing table. These columns need to either default to an value (which is fair) or be nullable.

TIL about the squircle

The code in the community's banner is in python 2. Can we get that changed?

A new community to request new communities instead of using the meta community. How very programmer of you.

Lots of people here lamenting about this. But the truth is that good code is easy to modify/delete.