Jacek Kołodziej
320 posts
Jacek Kołodziej
@Unit03
Programming keyboard cat @allegrotech. Also: photography, running, hiking and metal. @[email protected]
Warsaw, Poland Katılım Şubat 2008
119 Takip Edilen146 Takipçiler
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
Tallinn, Estonia 🇪🇪 English
YouTube
English
[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. meetup.com/allegrotech/ev…
Transmisja na Fb i YT youtube.com/watch?v=YjVrF_…. Zapraszam 😊
YouTube
Polski
I published something! A high-level overview of managing dependencies in a #Python project kolodziejj.info/articles/depen…
Yes ✅ it distinguishes libraries from applications.
Let me know what you think 🤗
English
Linki i slajdy: kolodziejj.info/talks/pyspark-…
Nagranie podlinkuję, jak tylko będzie dostępne :)
Polski
[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: na.allegro.pl/atm-natura Infrastructure: na.allegro.pl/atm-mrok UX & Product: na.allegro.pl/atm-blask ML & Big Data: na.allegro.pl/atm-fantastyka Security: na.allegro.pl/atm-fortyfikac…
Polski
Jacek Kołodziej retweetledi
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?
GIF
English
Jacek Kołodziej retweetledi
#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:
asciinema.org/a/411567
And here's the instructions on DevGuide
#renaming-branch" target="_blank" rel="nofollow noopener">devguide.python.org/gitbootcamp/#r…
English
Jacek Kołodziej retweetledi
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:
discuss.python.org/t/python-3-8-1…
English
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: twitch.tv/pablogsalgado. Come and join us 🚀
English
@zsiciarz Do you think my glorious single-sentence docstring addition could have been crucial in some way? ;D
English
So my humble typo fixes are now flying on Mars.
(Yeah, I don't think the copter uses requests+werkzeug onboard, rather the mission control software does. But it sounds cool!) #MarsHelicopter #python
English
Jacek Kołodziej retweetledi
English
_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.
English
How much time would you take from the development time (or any other activity) and give to repo history maintenance (writing useful messages etc.)?
English
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 ;) ).
English
@VeruuKabatova I agree with all that - let me expand on the original tweet twitter.com/Unit03/status/…
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
English
@Unit03 Real life example: A asked me why X was done. After digging through git I found A's OWN COMMIT "add X" 🤦♀️
People can read the code and see WHAT is being done. What the commit message needs to have is explaining WHY the change is needed, in more detail than "stop crashes"
English