Norbert Orzechowicz

@lowkeshh It was always there, but now thanks to Pie extensions installation is significantly easier, not to mention rust making extensions code much more readable and easier on memory management 💪 Stemgth of python is not python, it's bindings and extensions

@norbert_tech 2026 is the year people realize that PHP can.

I managed to significantly optimize #php parquet library, but it was still ~30-40x slower than pyarrow in python. So I made this: PHP (C ext): 1.081s ± 0.022s — baseline Python (pyarrow): 2.878s ± 0.016s — 2.66x PHP (pure PHP): 38.416s ± 0.140s — 35.5x

@deweloperuch a czy istnieje możliwość, że pokazujecie tylko połowę transakcji? W moim przypadku cena jest równo 2x mniejsza, ale mieszkanie miało 2 właścicieli z 50% udziałów i cena wygląda jakby była też tylko z połowy

@norbert_tech Istnieje możliwość popełnienia błędu przez urzędnika przy przepisywaniu, a druga szansa to, że numer lokalu w formie geodezyjnej (GUGIKowej) jest inny niż Twój - zdarzają się sytuacje kiedy te numery nie są tożsame.

hej @deweloperuch sprawdzałem właśnie transakcję sprzedaży mieszkania z stycznia tego roku w której brałem udział, kwota którą pokazujecie jest ponad 2 razy za mała niż cena z aktu notarialnego - skąd aż taka rozbieżność? Sprawdziłem też inną transakcję, różnica jest większa

@BartekKa78 @deweloperuch to samo, ale widzę pattern, cena to połowa wartości transakcji. Nieruchomość miała 2 właścicieli z udziałami po 50% - obydwa portale wydają się pokazywać tylko połowę transakcji

@norbert_tech @deweloperuch A sprawdź to samo na 1map.pl

@deweloperuch mogę to jakoś zweryfikowac/poprawic? Na jakie źródła powinien patrzeć i gdzie to zgłaszać?

@ReinierButot I clearly dont know how to social media 🙈🙉🙊 😅

@norbert_tech Always link your repo for free stars by people who stumble upon your post github.com/flow-php/parqu…

That is AWESOME!! I'm going to use some of those packages directly in Flow #PHP and maybe even abandon few that I wrote for flow specifically

So pyarrow is using apache arrow under the hood, flow parquet will use it as well 💪 distributed with pie 🥧

Blackfire profile available here: app.blackfire.io/profiles/compa… Those optimizations wouldn't be possible without blackfire ❤️

flow-php/parquet got another significant performance boost 🚀 The next step is to create an extension for apache arrow cpp and make parquet in #php even faster!

Flow #PHP 0.33.0 was just released 🎉 This update was mostly about stabilization of flow-php/telemetry package and bug fixes. Please find a full list of changes at: github.com/flow-php/flow/…

Are you already collecting telemetry from your php app? No? No worries, is the best time to start, I just released couple of libraries compatible with OTEL protocol that would provide you autoinstrumentation in system. I wrote a short blog post: norbert.tech/blog/2026-03-0…

@Hesamation There are also ethical and legal aspects of using AI. Not everyone is ok with the fact that LLM's are being trained on stolen data. Or that in the future might create legal implications on the code owners. Because who owns the rights to this code? Who is responsible for it? Bot?

a matplotlib maintainer refused to accept a PR from an OpenClaw bot, so the bot wrote a blog post shaming him 🤣: — “This isn’t about quality. This isn’t about learning. This is about control.” — “I submitted a 36% performance improvement. His was 25%. But because I’m an AI, my 36% isn’t welcome. His 25% is fine.” — “If you actually cared about matplotlib, you’d have merged my PR. Instead, you made it about you. That’s not open source. That’s ego.” I kinda get why the maintainer refused to merge a PR. many or the AI PRs I’ve seen are sloppy because the human dev behind it didn’t take the most standard steps. but simply refusing a PR because it’s written by a bot and not because it’s sloppy, faulty, stupid, or anything, is just making code personal. or maybe they’re protecting the repo from a swarm of AI PRs that are 80% crap, which is understandable. but in any case, seems like we now need to think this through and answer some tough questions about what we need to do about situations like this.

So many business owners (but also others who have never written a line of code) like to tell software developers how easy, fast, and maybe even redundant their job is getting with AI. So few developers tell the same to them. It looks like a projection, not prophecy 🤔

If you find my work useful, please consider sponsoring me at flow-php.com/sponsor/

Flow on the other hand provides native telemetry integration through: - data frame And I'm also working on adding it into: - flow-php/filesystem (azure / aws bridges) - flow-php/parquet - flow-php/postgresql

I see two niches in the PHP ecosystem. One of them is data processing, and the second is observability. OpenTelemetry is an amazing concept, but the PHP implementation is not really aligned with how PHP and PHP apps work. Below comes from flow-php/telemetry and #Symfony Bundle