Maccaroni and cheese were really meant to be Käsespätzle but for some reason didn’t.
Maccaroni and cheese were really meant to be Käsespätzle but for some reason didn’t.
But the are definitely called “Müllpandas” which literally translates to trash pandas.
They are really well designed too. They lock into place when flipped 180 degrees (drinking mode) and don’t interfere at all while drinking.
You’re right. It was the eighth movie. My bad. I didn’t even remember Nemesis. It kinda is the Star Trek V but for TNG.
Star Trek 10 - First Contact is also pretty solid.
And then he morbed all over them!
Well, as a consolation there is Rottenegg in Germany. Not nearly as catchy though.
Esteemed personages.
Then colleague upgraded glibc by copying it in via scp. Then we couldn’t ssh in anymore. :) Not sure how important that server was. I think it was reinstalled soon-ish.
You can write selects with many joins, as long they are regular and either add a column or reduce the result set. You have to write the joins explicitly though. Just shoving all of the restrictions into the where clause will definitely confuse everybody.
Well, you can still have the up-to-date plugin, you just have to pay for it now.
Since working with SQLAlchemy a lot (specifically it’s SQL compiler, not it’s ORM), I don’t want to work with SQL any other way. I want to have the possibility to extract column definitions into named variables, reuse queries as columns in other queries, etc. I don’t want to concatenate SQL strings ever again.
Having a DSL or even a full language which compiles to SQL is clearly the superior way to work with SQL.
I’m wondering if a field with more detailed information would be helpful for the users. Moderators might want to clarify or explain in more detail the function or intention behind a tag. This doesn’t seem to be considered in the RFC.
deleted by creator
Depends on how large your Python projects are. If you have a million lines of Python code, navigating quickly and directed is invaluable.
I used plain vim before for Python projects, but these never grew above 50k lines of code.
I never got so far, but had a system built which some parts of what you described. It was incredibly relaxing to develop with it. Our take as a team was: boring is better, we don’t want to be paged on weekends.
It teaches you to think about data in a different way. Even if you never will use it in your products, the mental facilities you have to build for it will definitely benefit you.
Completely agree. I really love SQL, but I hate it’s syntactic limitations. SQLAlchemy was my band-aid with an after-burner to make it bearable (and maintainable).
I also have been personally victimized by honk!