Jacek Kołodziej

Programming keyboard cat @allegrotech.

Also: photography, running, hiking and metal. @[email protected]

[Jacek Kołodziej @Unit03]

@starenka Unfortunately not this time, no 😭

[Jacek Kołodziej @Unit03]

This 🤗

The slides and links are available at https://t.co/If5YCWbrPU

#PythonGIL #cpython #gil

[PyCon Estonia @PyConEstonia]

We're excited to announce our next speaker, Jacek Kołodziej! Join us as he dives into the intriguing world of Python's GIL 🐍💡. Curious about its impact? Wondering if you should care? Don't miss this insightful talk! 🗣️🇪🇪 #PyConEstonia2023 #PythonGIL @Unit03

[Jacek Kołodziej @Unit03]

What's up with #CPython's #GIL in 2023?

I will be presenting its:
* past
* present (including how to deal with it)
* and (non-?)future

at @PyConEstonia next week. :)

https://t.co/41Ffq9bnre

#python

[Piotr Kowalski @piecioshka]

I am a fan of slides created by @Unit03 😊 on talk
https://t.co/lhJD2AejHw at #pywaw @PyWaw

[Jacek Kołodziej @Unit03]

@piecioshka @PyWaw Awww, thank you!

[Jacek Kołodziej @Unit03]

[PL only] Na dzisiejszym (18:00) @allegrotech Live będę mówił o tym, jak żyje się nam w zespole używającym na co dzień i Pythona, i stosów JVMowych. https://t.co/V5H0ODUH0L

Transmisja na Fb i YT https://t.co/vEziiDC5Wa. Zapraszam 😊

[Jacek Kołodziej @Unit03]

I published something! A high-level overview of managing dependencies in a #Python project https://t.co/kLq1S8yFXh

Yes ✅ it distinguishes libraries from applications.

Let me know what you think 🤗

[Jacek Kołodziej @Unit03]

Linki i slajdy: https://t.co/I2udX4h9Aa
Nagranie podlinkuję, jak tylko będzie dostępne :)

[Jacek Kołodziej @Unit03]

[Polish only] Za 40 minut będę mówił o tym, jak wybrać między Scalą a Pythonem przy korzystaniu z Apache Spark ✨ 18:20, ścieżka ML & Big Data ("Fantastyka"), zapraszam🤗

[allegro.tech @allegrotech]

We are live now with 5 Tracks at Allegro Tech Meeting 2021!
Software: https://t.co/AmGjcM0CHY
Infrastructure: https://t.co/YM2Jyd2XRN
UX & Product: https://t.co/HNS2F2reTe
ML & Big Data: https://t.co/s5MVhQla54
Security: https://t.co/PZMU2GXEoT

[Daria Grudzien — now @[email protected] @DariaGrudzien]

Anyone willing to mentor on #grafana , #prometheus, and #observability in #AWS context?

I'm new to the topic and in a desperate need to conquer the learning curve. Pretty please?

[Mariatta 🤦 @mariatta]

#Python The default branch on the CPython repo has just been changed to `main`.
I've updated my local clone of CPython, and you can do it too!
Here's my the asciinema showing how to do it:
https://t.co/IonVElTSdg
And here's the instructions on DevGuide
https://t.co/ZXTJGslPEE

[Łukasz Langa @llanga]

Python 3.8.10 is the last regular bugfix release for the 3.8 series, moving to security fix-only mode.

Upgrade to 3.9 to keep receiving bugfixes, preferably to 3.9.5.

With 3.10.0 beta 1 you're invited to test-drive your projects with 3.10.

All out now:

https://t.co/wllBB49uV6

[Jacek Kołodziej @Unit03]

Next Python release (3.10.0 beta 1) being released _live_ right now on Twitch 🤩

[Pablo Galindo Salgado @pyblogsal]

I will be streaming the release of Python 3.10 beta 1 🐍 1in 1 hour here: https://t.co/1cnWKviM2y. Come and join us 🚀

[Jacek Kołodziej @Unit03]

@zsiciarz Do you think my glorious single-sentence docstring addition could have been crucial in some way? ;D

[Neuralink @neuralink]

Monkey MindPong https://t.co/7zstTZ1X1w

[Jacek Kołodziej @Unit03]

@javifields @TheOldReader Looks down to me, too. :( https://t.co/0R8AfCNaoh

[Jacek Kołodziej @Unit03]

@Hamatti @0lpeh Me too. :) It's just good commit msgs have their value, clean code has its value, well prepared features have their value, features shipped early have their value etc. - and time off has its value too. I'm trying to see how to strike a balance there.

[Jacek Kołodziej @Unit03]

_That being said_, there's another question: how much do you _actually_ value the commit messages and orderly commit history in general?

Where do you strike a balance between the maintenance cost vs. value the commit history provides?

Any good articles about it?

[Jacek Kołodziej @Unit03]

@peter_podgorski There's a third way: shape the individual commits to 1) be atomic* changes that 2) best explain the context and the "why" of the change in the long run.

The exact tool (squashing, rebasing, cherry-picking) is less important, use whatever you like.

[Jacek Kołodziej @Unit03]

How much time would you take from the development time (or any other activity) and give to repo history maintenance (writing useful messages etc.)?

[Jacek Kołodziej @Unit03]

That's where my question came from. :) How to value the repo history maintenance against the rest of the maintenance, assuming the time being a limited resource ('cause it is ;) ).

[Jacek Kołodziej @Unit03]

@VeruuKabatova I agree with all that - let me expand on the original tweet https://t.co/Y8NGwf5tVb

[Jacek Kołodziej @Unit03]

1. I'm absolutely pro having a clean repo history with a lot of "why" and context in commit msgs
2. I'm doing it myself pretty much everywhere (company/open source, doesn't matter)
3. The more I do it, the more proficient I am, the less obstacles for doing it more