Notices by Borutzki (borutzki@mastodon.social)

@kuba Tyle dobrze, że nie tylko ja zauważam ten problem. A po nałożeniu go na słabą dokumentację (lub jej brak), chaos informacyjny to nawet nie tyle kwestia czasu, co po prostu smutna rzeczywistość.

@kuba Dajmy im z pół roku, to może przy okazji wygenerują sobie też słuchaczy :D

I need to use two different Outlook / Teams accounts at once in my browser for my job and in this case, #Firefox Containers is the thing. With two clicks you can start new session of any service fresh and don't have to login again and again in incognito mode.

In case you wonder how to use it - right-click the new tab button and choose a new context you want to use. That's all.

Just wanted to share, maybe not everyone here is aware that this thing exist 🦊
https://support.mozilla.org/en-US/kb/how-use-firefox-containers

@wariat @kuba Wait, a w jaki sposób to dokładanie się do branży tytoniowej tu działa? Podrzuciłbyś jakiś artykuł? Brzmi ciekawie, nigdy wcześniej nie słyszałem.

@arek na LinkedIn komentarze chyba można generować przez autosugestie, więc kto wie, czy dyskusje na LinkedIn już teraz nie są dysputami AI vs. AI :D

@arek ja najbardziej lubię te dyskusje typu:

Osoba A: Trzeba mieć otwartą głowę na nowe pomysły i słuchać nowych idei <tu jakaś techniczna wstawka>
Osoba B: <nt. technicznej wstawki> no ale tu robisz błąd, to nie tak działa
Osoba A: Jestem ekspertem, od 10 lat działam w branży, <blablabla>, totalnie się z Panem nie zgadzam, Pan nie wie o czym mówi

XD

@arek w kółko te same historie i dramy, ale przynajmniej nowej pracy można łatwo poszukać :)

Yesterday I had quite stressful job interview, so there was no #DailyPythonista.

But here we go again. And again with a quick one.

Do you know underscore symbol? The "_" one. Probably so.

In Python, it has two main usages.

First, it's an unnamed variable. You can use it when unpacking tuple (or any other sequence) to "throw away" unneeded values. 🚮

Second, it's the reference to output of previous expression in interpreter. Quite handy if you use #Python as your main calculator on PC. 🧮

Ah, let me share with you that weird thought process I was into today.

So, there's that huuuuge class (~1500 lines) in our repository. It's a wrapper for some API that may be used in another API - kind of layer of abstraction, with some simple data operations in between (like translating names and variables).

My starting point was: how can I get this huuuuge class split across multiple smaller classes?

#python

Well, "if not composition, then maybe inheritance". I thought.

Then I started doing this kind of refactor, like splitting methods into separate classes, based on functionality.

And guess what - I've achieved nothing. Like, I still have to share the same internal state, but now I have e.g. 4 different big classes and one kind of "god object" that subclasses them all.

Basically, there is no added value, because code is the same and I've only added inheritance to existing composition.

So the first solution was: "let's play with composition".

But there is no way to get it well at composition. I already have this API class that is an internal object of my class, and all methods in my class touch this internal class.

And this internal API class is also a huuuuge (~2000 lines) class which I am not the owner of.

So, composition here is probably not a good advice, as it already is on the board...

Now you see where it goes. I have one huuuuge class with 1500 lines of code and corresponding unit test file similar in size.

And all options to change it, are "complicate it more so it may seem simpler".

You see where it goes? To adding additional layer of abstraction to achieve nothing.

Okay, so composition is there and inheritance adds no value. Then what?

At first, I thought: maybe some more "pro", like mixin classes? Well, this would not only add the burden of subclassing but also make me explain my colleagues what do I mean with "this class won't work on its own".

Maybe I could split the class into independent classes?

Maybe - but this still similar code, using the same API underneath, but now it has multiple names and connect/disconnect methods.

Of course I'm open to new ideas that fedipeople may give me on that. If you have any - let's share experiences. I've already shared mine ;)

#python #programming #softwarearchitecture

So, you know what I'll do with that?

I'll probably stick with this huuuuge class. It's already simple and complicated at once. And seems like I can only sacrifice "simple" without reducing complexity.

All in all, it seems better to have it all in one class and go `CTRL+F` in my IDE (or use autocompletion) instead of creating structures that may result in some smaller classes, with no reasonable explanation for these classes other than "their smaller".

@kuba fajny artykuł, dzięki za podrzucenie :D

Zastanawiam się, jakby tu podejść do tematu od strony wyrabiania nawyków. No bo OK, mogę odstawić kawę, ale prostsze wydaje się zastąpienie jej czymś innym.

Tylko czym? Inką? Szlugiem? Herbata raczej odpada...

@Gargron what’s “German train hell”?

@nixCraft for Monday, coffee is the best.

But when I feel sad at Friday afternoon, I deploy something to feel better.

@icd @ola @kuba
w sumie udało Wam się mnie przyciągnąć tematyką podkastu i powiem to głośno: robicie świetną robotę ;)

Chyba po prostu brakowało mi jakiegoś przekrojowego źródła informacji w tematach prywatności w sieci. Brakuje mi czasu na przeglądanie wszystkich afer i nowinek, a u Was wszystko jest w jednym miejscu. Szacun!

@kuba ktoś chyba lubił hamowanie z driftem ;)