With the internet melting over the PHP2Shell vulnerability, seeing PHP all over the news actually brings me back to great times. If not for PHP, I might never have started my software development career. I was 16 or 17, making pocket money freelancing and doing ⁠psd2html⁠ work (yes, the kind of tasks you can now vibecode in 5 minutes). One of my customers asked me if I knew PHP. "Of course," I said... Well, I didn’t. Back then, my internet wasn't even fast enough to download a local server or the documentation. So I went to a store, bought a physical CD with PHP on it (photo of the CD attached!), and opened up the manual. Fortunately, I had a printer at home, so I printed out about 100 A4 pages of PHP syntax and documentation. That weekend, I had to take a train to the countryside to visit my grandma. I took that stack of 100 pages with me and read it the entire train ride - and kept reading at my grandma's house, since there was literally nothing else to do there besides hugging her and having a quick catch-up. Two days later, I came back home, pinged my client on ICQ, and said: "Give me more details about this PHP project of yours." And just like that, my software engineering career began. Things snowballed quickly from there: Later that same year, I landed my first full-time PHP developer job at Warecorp and spent a couple of years there as a Lead PHP Developer, largely because my English was good enough to talk directly to American clients. Next, I joined Oxagile (which is where the team photo is from!). Our whole PHP crew decided to get officially certified together, and we all passed our Zend PHP certifications. From there, I moved to EPAM. At the time, EPAM was heavily focused on massive Java enterprise projects and didn't really have a PHP practice. I ended up leading a team of ~20 PHP developers, building high-traffic platforms for MTV Entertainment - including MTV dot com, UFC, and Comedy Central. I had no idea back then where it would all lead, but following what genuinely sparks your curiosity pays off if you just keep showing up and building on that path. P.S. Speaking of PHP... it’s probably a great time to go update your WordPress blogs. 😉

Excited to share that I’ve been promoted to Chief Product Officer of Air Platform at @jetbrains The future of AI-native software engineering isn’t just a single coding agent—it’s a unified system where developers, teams, and agents work together seamlessly. Here is what we’re building next 🧵👇

And got to see in the flesh @JensenHuang Nvidia CEO

Junie team joined RTX Spark launch party

@kskrygan presents JetBrains Air at @WorldSummitAI JetBrains Air is new system for building software with agents

@junie_ai team is attending Gemini 4 Argon evaluation workshop. The latest model from @GoogleDeepMind

GPT 6 Astra is painting San Francisco

The Evolution of Voice as UI: 1. Hardcoded Intents: TTS and STT have been largely solved for years, but early assistants like Siri and Alexa relied on rigid, prescripted intent mapping. 2. Raw Transcription: Voice input just captured verbatim speech filler words, false starts, awkward pauses, and all. 3. LLM Cleaners: Tools like Whisper Flow arrived, using LLMs as a harness to turn messy human speech into structured, coherent text prompts. 4. Multimodal Local Agents: Systems like Codex integrated voice with vision and direct on-device action. 5. Remote Agent Control: With Meta Muse and OpenAI's latest agentic workflows, the compute is entirely remote. Hardware like Meta RayBans or your phone becomes pure audio I/O, an ambient steering wheel for an agent running a full computer in the cloud.