Jarosław Pałka
where else to find them
no profile links on file
what they talk about
all 8 in the filters
where they keep going back
all 5 in the filters
on a stage with
- Michał Jonkoonce
who talks about the same things
- Jakub Kubryński15 talks
- Rafal Leszko20 talks
- Alessio Coltellacci6 talks
- Andrzej Grzesik24 talks
- Sławomir Sobótka16 talks
- E. Bernard10 talks
| title | conference | date |
|---|---|---|
| When a Java Programmer Meets C | JNation 2026 | 2026-05-26 |
Java 22 exposes a Foreign Memory & Foreign Function API that lets code allocate off‑heap via memory segment arenas (global, confined, shared), define C‑style… | ||
| episode 1 | JDD 2025 | 2025-10-21 |
A podcast episode introducing Jarosław Pałka from the JDD conference Program Council, promoting the upcoming JDD 2025 event and inviting listeners to learn… | ||
| Performance tests and other lies | GeeCON 2024 | 2024-05-15 |
Eight practical anti‑patterns and concrete fixes: use percentiles and histograms instead of averages, prefer JMH for Java microbenchmarks and combine JMH with… | ||
| Everything You Don’t Want to Know About Concurrency on the JVM | JDD 2023 | 2023-10-24 |
The talk examines JVM concurrency mechanisms—synchronized (monitors), ReentrantLock, and java.util.concurrent.atomic types—comparing their implementations and… | ||
| Bare metal Java | GeeCON 2023 | 2023-04-19 |
Argues that recent Panama APIs make the JVM far more hardware-friendly: MemorySegment (spatial, temporal and thread-confinement bounds) plus MemoryLayout let… | ||
| Bare Metal Java | Confitura 2022 | 2022-06-25 |
Describes Project Panama’s native memory and FFI features for Java 17/19: MemorySegment and ResourceScope for safe lifecycle control, MemoryLayout and… | ||
| Interview with Jarek Pałka | 4Developers 2015 | 2015-04-20 |
Jarosław Pałka describes his 10+ years in IT working as a DBA, developer, architect and manager across waterfall and Agile projects, arguing that simplicity… | ||
| Dekonstrukcja architektury w czasach kryzysu. | JDD 2012 | 2012-10-25 |
Argues that software problems are systemic not technical, using systems thinking and complexity theory to explain architecture crises: stocks and flows… | ||
| nothing matches | ||