Georg Unterholzner
@georg.dev
👨🏻💻 Software engineer @Dynatrace
🌐 Web dev and trained data scientist
🍜 Foodie | gym-goer | tech & gaming nerd
🇦🇹 Based in Vienna
https://georg.dev
🌐 Web dev and trained data scientist
🍜 Foodie | gym-goer | tech & gaming nerd
🇦🇹 Based in Vienna
https://georg.dev
Pinned
Reposted by Georg Unterholzner
🛠️ If your team has issues to work through:
We do an exercise at offsites called Elephants, Tigers & Paper Tigers.
- Elephants are things that the group isn’t talking about but needs to
- Tigers are things threatening the team, risks
- Paper tigers are things that seem like risks, but aren’t
We do an exercise at offsites called Elephants, Tigers & Paper Tigers.
- Elephants are things that the group isn’t talking about but needs to
- Tigers are things threatening the team, risks
- Paper tigers are things that seem like risks, but aren’t
November 6, 2025 at 1:29 PM
🛠️ If your team has issues to work through:
We do an exercise at offsites called Elephants, Tigers & Paper Tigers.
- Elephants are things that the group isn’t talking about but needs to
- Tigers are things threatening the team, risks
- Paper tigers are things that seem like risks, but aren’t
We do an exercise at offsites called Elephants, Tigers & Paper Tigers.
- Elephants are things that the group isn’t talking about but needs to
- Tigers are things threatening the team, risks
- Paper tigers are things that seem like risks, but aren’t
Getting a full afternoon of uninterrupted coding is so nice.
I don't get that often but today is one of those days. Feels great!
I don't get that often but today is one of those days. Feels great!
August 19, 2025 at 4:41 PM
Getting a full afternoon of uninterrupted coding is so nice.
I don't get that often but today is one of those days. Feels great!
I don't get that often but today is one of those days. Feels great!
Sometimes programming just feels too much like Hänsel and Gretel.
August 18, 2025 at 3:20 PM
Sometimes programming just feels too much like Hänsel and Gretel.
Basic question but I can't figure it out. How are these two design patterns called?
In the first, the component structure is fixed, and behavior is controlled *only* through props serving as config.
In the second, an extension point via the children prop allows for more flexibility.
In the first, the component structure is fixed, and behavior is controlled *only* through props serving as config.
In the second, an extension point via the children prop allows for more flexibility.
August 13, 2025 at 1:58 PM
Basic question but I can't figure it out. How are these two design patterns called?
In the first, the component structure is fixed, and behavior is controlled *only* through props serving as config.
In the second, an extension point via the children prop allows for more flexibility.
In the first, the component structure is fixed, and behavior is controlled *only* through props serving as config.
In the second, an extension point via the children prop allows for more flexibility.
Don't be like me.
Don't sleep on @playwright.dev's test steps.
It took me 4 years to realize how much cleaner, readable, and debuggable my tests could be.
Named steps = better readability, clearer reporting, faster debugging.
Check out the before/after!
Don't sleep on @playwright.dev's test steps.
It took me 4 years to realize how much cleaner, readable, and debuggable my tests could be.
Named steps = better readability, clearer reporting, faster debugging.
Check out the before/after!
August 1, 2025 at 10:07 AM
Don't be like me.
Don't sleep on @playwright.dev's test steps.
It took me 4 years to realize how much cleaner, readable, and debuggable my tests could be.
Named steps = better readability, clearer reporting, faster debugging.
Check out the before/after!
Don't sleep on @playwright.dev's test steps.
It took me 4 years to realize how much cleaner, readable, and debuggable my tests could be.
Named steps = better readability, clearer reporting, faster debugging.
Check out the before/after!
Some tools force you to learn a complicated API and require constant maintenance.
Other tools... just work, and that's why it's easy to overlook them.
@openfeature.dev is one of those tools.
Do I use it daily? Yes.
Do I ever have to think about it? No.
Other tools... just work, and that's why it's easy to overlook them.
@openfeature.dev is one of those tools.
Do I use it daily? Yes.
Do I ever have to think about it? No.
July 30, 2025 at 2:23 PM
Some tools force you to learn a complicated API and require constant maintenance.
Other tools... just work, and that's why it's easy to overlook them.
@openfeature.dev is one of those tools.
Do I use it daily? Yes.
Do I ever have to think about it? No.
Other tools... just work, and that's why it's easy to overlook them.
@openfeature.dev is one of those tools.
Do I use it daily? Yes.
Do I ever have to think about it? No.
Finally moving all my pet projects off Travis CI. Not a fan of their expiring credits billing model.
But where to migrate?
- Circle CI
- GitHub Actions
- ...?
What’s your pick?
But where to migrate?
- Circle CI
- GitHub Actions
- ...?
What’s your pick?
July 28, 2025 at 12:36 PM
Finally moving all my pet projects off Travis CI. Not a fan of their expiring credits billing model.
But where to migrate?
- Circle CI
- GitHub Actions
- ...?
What’s your pick?
But where to migrate?
- Circle CI
- GitHub Actions
- ...?
What’s your pick?
I was frustrated with the lack of clear advice on setting up copilot_instructions.md. Most guides are vague, or worse, generic AI slop that *hurts* Copilot's performance. So I experimented and found better ways to make Copilot *actually helpful*. 🧵
July 22, 2025 at 12:35 PM
I was frustrated with the lack of clear advice on setting up copilot_instructions.md. Most guides are vague, or worse, generic AI slop that *hurts* Copilot's performance. So I experimented and found better ways to make Copilot *actually helpful*. 🧵
Stack Overflow, are you alright?
July 17, 2025 at 9:35 AM
Stack Overflow, are you alright?
Finally!!
Grok 4 in GitHub Copilot.
Grok 4 in GitHub Copilot.
July 14, 2025 at 3:03 PM
Finally!!
Grok 4 in GitHub Copilot.
Grok 4 in GitHub Copilot.
Gen Alpha successfully rotted my brain. grid-template-columns: 1fr 2fr; now reads “one for real, two for realz.”
My grid is aggressively verified. ✅
My grid is aggressively verified. ✅
June 28, 2025 at 5:36 PM
Gen Alpha successfully rotted my brain. grid-template-columns: 1fr 2fr; now reads “one for real, two for realz.”
My grid is aggressively verified. ✅
My grid is aggressively verified. ✅
Crazy idea to utilize the webcam input. Mind-blowing.
had to try CSS filter + SVG glass displacement on webcam input – crank saturation for cheap gold ✨
June 23, 2025 at 12:16 PM
Crazy idea to utilize the webcam input. Mind-blowing.
This year's Stack Overflow Developer Survey in a nutshell
June 12, 2025 at 11:28 AM
This year's Stack Overflow Developer Survey in a nutshell
Large Language Models (LLMs) with "reasoning" capabilities are super hyped, but new research from Apple shows their "thinking" is often an illusion. Beyond a certain complexity, they fail completely. Key points in the 🧵.
June 11, 2025 at 12:50 PM
Large Language Models (LLMs) with "reasoning" capabilities are super hyped, but new research from Apple shows their "thinking" is often an illusion. Beyond a certain complexity, they fail completely. Key points in the 🧵.
To all GitHub Copilot users: What are your most-used features and shortcuts?
Inline chat? Agent mode? Just the autocomplete? 🤔
Inline chat? Agent mode? Just the autocomplete? 🤔
June 3, 2025 at 10:03 AM
To all GitHub Copilot users: What are your most-used features and shortcuts?
Inline chat? Agent mode? Just the autocomplete? 🤔
Inline chat? Agent mode? Just the autocomplete? 🤔
Austria is outrageously beautiful.
May 27, 2025 at 4:50 PM
Austria is outrageously beautiful.
my experience with firebase studio so far 😐
April 18, 2025 at 9:59 AM
my experience with firebase studio so far 😐
My learning for that day: the final solution was to use the render props pattern.
Kudos to @bhuynh.dev and @taranetz.com for pointing that out.
We can even take a step further by leveraging React's `isValidElement` function to support both render props and a standard child component.
Kudos to @bhuynh.dev and @taranetz.com for pointing that out.
We can even take a step further by leveraging React's `isValidElement` function to support both render props and a standard child component.
March 19, 2025 at 2:40 PM
My learning for that day: the final solution was to use the render props pattern.
Kudos to @bhuynh.dev and @taranetz.com for pointing that out.
We can even take a step further by leveraging React's `isValidElement` function to support both render props and a standard child component.
Kudos to @bhuynh.dev and @taranetz.com for pointing that out.
We can even take a step further by leveraging React's `isValidElement` function to support both render props and a standard child component.
Reposted by Georg Unterholzner
I have a passive theory that the manner in which junior and senior devs leverage AI assistance for coding is fundamentally different: (1/?)
March 18, 2025 at 4:38 PM
I have a passive theory that the manner in which junior and senior devs leverage AI assistance for coding is fundamentally different: (1/?)
March 11, 2025 at 4:33 PM
Life hack: you don't have to worry that someone could replace you with AI, if you replace yourself with AI.
March 8, 2025 at 4:20 PM
Life hack: you don't have to worry that someone could replace you with AI, if you replace yourself with AI.
React: passing state from a wrapper component to a child. How?
I'm building a library that exposes a single wrapper component. Users of this library add the wrapper to their TSX and nest their child component inside it.
The wrapper fetches some data that's relevant to the child component.
I'm building a library that exposes a single wrapper component. Users of this library add the wrapper to their TSX and nest their child component inside it.
The wrapper fetches some data that's relevant to the child component.
March 5, 2025 at 6:42 PM
React: passing state from a wrapper component to a child. How?
I'm building a library that exposes a single wrapper component. Users of this library add the wrapper to their TSX and nest their child component inside it.
The wrapper fetches some data that's relevant to the child component.
I'm building a library that exposes a single wrapper component. Users of this library add the wrapper to their TSX and nest their child component inside it.
The wrapper fetches some data that's relevant to the child component.
March 5, 2025 at 4:28 PM
React: passing state from a wrapper component to a child. How?
I'm building a library that exposes a single wrapper component. Users of this library add the wrapper to their TSX and nest their child component inside it.
The wrapper fetches some data that's relevant to the child component.
I'm building a library that exposes a single wrapper component. Users of this library add the wrapper to their TSX and nest their child component inside it.
The wrapper fetches some data that's relevant to the child component.