Peter Galiba (@Poetro) header
Peter Galiba (@Poetro) profile picture

Front-end developer mainly working with JavaScript, HTML, CSS and Node.js on the server.

London, England
Joined April 2007
Photo by Peter Galiba (@Poetro)Photo by Peter Galiba (@Poetro)Photo by Peter Galiba (@Poetro)Photo by Peter Galiba (@Poetro)Photo by Peter Galiba (@Poetro)Photo by Peter Galiba (@Poetro)Photo by Peter Galiba (@Poetro)Photo by Peter Galiba (@Poetro)Photo by Peter Galiba (@Poetro)Photo by Peter Galiba (@Poetro)
69
Peter Galiba retweeted
Az elég kemény. Ha még @hszhsz bankkártyás sztorijai nem voltak elég merészek, akkor itt van még egy lapáttal. Ha új kártyát kérsz, a kamu kereskedő azelőtt megkapja a kártyaadataidat, hogy hozzád eljutna :D elk.zone/mastodon.social/@ty…
3
2
6
792
One of Paul Muad Dib's quest on Arrakis was to test if he was an early bird.
70
I still can't get over how bad AI has become. And this is coming from a computer scientist who spent over a decade studying and programming AI. I fucking LOVE AI, but here are 10 reasons I absolutely fucking hate it now, a 🧵 ...
570
11,878
1,301
48,783
5,986,375
Stand-up comedian Aurie Styla, a 90s nerd, takes an autobiographical journey through technology history.We begin in the early 90s, with the tinny sound of the Nintendo Game Boy and his first 13-inch television * Episode Download link (14 MB): open.live.bbc.co.uk/mediasel…
109
Peter Galiba retweeted
Did @ryanflorence's Let Me Be talk make a compelling case for not using const? Was it clear what we should do or not do by the end? And why we should or shouldn't do it? In this week's video I look critically at the talk point by point.
7
6
6
82
89,103
Peter Galiba retweeted
One of the coolest things that happens every year: the @webaim Million study. It analyzes the top 1,000,000 home pages to check for accessibility errors. The 2024 report is out, and it’s a very interesting and informative read, do check it out! lnkd.in/gzTaxfR Here’s the bad news: 96% of home pages have bugs. This means that a great number of people with disabilities can’t easily interact with the web. And it IS everyone’s right to access the services available on the web. Now the good news: the most common bugs are easy to fix or avoid. Seriously, they are easy to fix. And no, this is not saying that accessibility is easy. The more complex a site, the more head scratching the accessibility aspect of it. But this is an expected progression in frontend in general, and in our journey to become developers. We start with adding a click event on a button, and months later we worry about managing state in React with useReducer. So, if you haven’t thought about accessibility yet, start with the basics. And know that it will make a big difference in the life of a person with disabilities. Let’s learn how to avoid the 6 most common, very easy to fix bugs. Check out this article I wrote to start looking for these bugs in your portfolio site or projects. Please reach out if you have any questions. lnkd.in/eWfW8aAf Let's make it accessible!
1
7
12
724
Did you know why they skipped Angular version 3? Because it would have been triangular!
1
4
162
All this ditching TypeScript notion that emerged recently sets a dangerous precedent. As things often are online, people seldom go into due detail when explaining decisions. Bright titles scream the loudest, I suppose. I should probably put this into an article but I'll start from here. One of the common complaints about TS is the need to bring in a compilation step. Despite the compilers being generally fast, with experimental third-party compilers even bringing that to outstanding speed, I share the outlook that no compilation is the best outcome. But that hasn't been the case for JavaScript (yes, you've not misread) for almost a decade now. Apps were built by Babel when I started my engineering career in 2016, and they are still built by Babel or other tooling. The compilation step was always there, and I dare say it will remain there, regardless if you're using tools like TypeScript or not. The community has long seemed to realize that same as CSS and HTML are unmaintainable in their raw form, so is JavaScript. There will always be a shiny Stage 0 experimental syntax you want to try. There will always be browser-specific bugs. There will always be the need to mangle, compress, minify, sign, tree-shake, dedupe... You will always need a compiler. ESM tries to bring modern JavaScript to the browsers. I don't know in what universe the folks live who abandon TypeScript, but the last time I checked ESM-only web is but a distant dream. Five years from now, maybe. Likely ten. Let's speak about it when that time comes. The second most common complaint is the mental and resource overhead when writing types. I get it, types are hard, they are. Nobody wants to spend time fighting a nested generic when there are features to ship or bugs to be fixed. Until you realize that time spent on types pays off. Suddenly, feature releases get smoother, and bugs are caught even before they are pushed to remote because type-checking is, essentially, a static test. I don't hear folks complaining about other strictly-typed languages. Somehow, there, over the hill, the type-safety makes sense, but not in TypeScript, no. I never understood that. Perhaps people who claim this have never seen a production database go down due to a wrong data type being written. Or never fixed issues where a chunk of data suddenly changes its type 10 levels down the transformation tree. Or never seen plain JavaScript cause products to loose revenue and customers due to the poor quality of the written code. Writing pure JavaScript is like trying to cut a watermelon with a chainsaw in the dark. It sounds fun and free and quite easy until there's a roomful of mess to clean up. I suppose some can live and thrive in that mess. In the end, everyone decides for themselves. I've been using TypeScript for 4 years now and I'm not planning to switch to anything else. It's a unique tool in its proximity to plain JavaScript and high return values that have been helping me ship reliable code for years. It's also a well-written and actively maintained tool, which only plays in its favor.
62
96
23
784
156,431
I cannot POSSIBLY be any clearer (as someone who worked in IT managing some of this country's biggest databases) UNDER NO CIRCUMSTANCES SHOULD ANYONE PROVIDE PICTURES OF THEIR PASSPORTS OR DRIVING LICENCES ESPECIALLY NOT to databases outside the GDPR THREAD:
X will begin to have users verify their identity by having them submit a selfie alongside a government issued ID. The process requires users to consent to X storing their information for 30 days and sharing it with AU10TIX, an identity verification company based in Israel.
Readers added context they thought people might want to know
ID verification is going to be an optional layer of verification for X Blue users. This is not going to affect non-Blue users in any way. socialmediatoday.com/news/x-may-soo…
446
13,886
786
33,255
5,795,650
“Coding is to programming what typing is to writing.”—Leslie Lamport @changelog changelog.com/podcast/552 – at Martinsburg, WV
2
3
6
1,667
Peter Galiba retweeted
Modern react's recommended way of piling all application concerns onto components is the worst and creates unmaintainable tangled spaghetti. React should focus on the one thing it always did well: UI=fn(props) If it doesn't put pixels on the screen, it shouldn't be in react.
Quote tweet this with your spiciest web dev take
2
11
127
20,706
Me: I'm afraid of JavaScript keywords Therapist: tell me about this Me: 😱😱😱
52
88
8
646
64,986
If you're a software engineer, your main job is maintaining legacy code. Why? Because building a system doesn't take long, in comparison to how long code will last, assuming the code/business are successful. Here are the 10 commandments of maintaining legacy code. 🧵
24
343
35
1,668
242,879
Do you remember when you joined Twitter? I do! #MyTwitterAnniversary