I found something crazy - my #swiftstudentchallenge idea draft! π€©
It was made during work, on a coffee break, as a concept sketch for #WWDC 21 submission. It was second online #AppleEvent. βοΈ
The final app turned out almost exactly the same, and it won an award! π₯³π
10.03.2026 22:54
π 2
π 0
π¬ 0
π 0
It still impresses me: a long, detailed prompt with described tech (and even server) requirements, and I have a ready promo page for the project. π
Whatβs next? Today I got up to 50% of the #ZarazJade refactor. π
I still have so much ahead of me. πͺ
#BuildInPublic #DevDiary
09.03.2026 17:07
π 1
π 0
π¬ 0
π 0
Okay... Calm down... Donβt make any sudden movements...
Itβs less than three weeks... You can do it... You are patient. You are strong!
06.03.2026 22:03
π 1
π 0
π¬ 0
π 0
I'm starting to worry that 64 GB of RAM might not be enoughβ¦ π€ͺ
Waiting for the new #M5Pro...
05.03.2026 21:43
π 0
π 0
π¬ 0
π 0
Okay - a lot of wisdom here, but what next? Nothing. Learn, combine it, and get better every day. π¨βπ»
Remember: some companies will win big and others will lose by missing the opportunity or following the lobby.
Success doesnβt come from technology, but from the work of people.
04.03.2026 13:01
π 0
π 0
π¬ 0
π 0
So the risk is not in the AI, but in the approach.
For product, these tools boost productivity. Tech Leads should drive implementation and ensure the right technical conditions. AI is as good as the technical vision of the entire project.
Creativity is still the domain of devs.
04.03.2026 13:01
π 1
π 0
π¬ 1
π 0
Of course, weβll find perfect examples where everything looks like a book. π But weβll also see overgrown projects with an incredible amount of boilerplate code π».
Thatβs why we need #architects ποΈ to plan urbanity in our apps so we donβt repeat mistakes from other industries.
04.03.2026 13:01
π 0
π 0
π¬ 1
π 0
Neither of these two, even if the cost is temporary chaos in tech projects.
Learning is a continuous process, and part of it is new tools. Unfortunately, companies looking for profits often introduce tools hoping for #optimization, but they forget about the implementation stage.
04.03.2026 13:01
π 0
π 0
π¬ 1
π 0
Itβs easier to judge changes in hindsight, seeing both good and bad examples but there are always more edge cases. π¨βπ¬
That's why I want to compare the current boom in the creation of technical projects in #VibeCoding mode to that dynamic period. π
Should we adapt or fight? π€
04.03.2026 13:01
π 0
π 0
π¬ 1
π 0
π¨Attention! Controversial post about #AI and #Agents!
I wonder if you have similar feelings.
The promo of #AgenticCoding reminds me a bit of the automotive advertising methodology in the USA in the 1960s. The lobby works, the market implements, and people follow the new trend.
04.03.2026 13:01
π 3
π 0
π¬ 1
π 0
@EEhare it would be amazing to try to collect all these amazing projects here!
#DubDub! π₯³
03.03.2026 10:59
π 0
π 0
π¬ 0
π 0
Iβm super excited about the first submissions for the #SwiftStudentChallenge! I review every PR and leave a short comment. Amazing work - congratulations! π
Do me a favor and add your project. Itβs amazing to see your creativity!
#WWDC
Please share! π
github.com/wwdc/2026
03.03.2026 10:59
π 0
π 0
π¬ 1
π 0
I have to get back to my frames with #WWDCPins πΈ. Maybe Iβll be able to finish them by June ποΈ.
Todayβs pin is a fine addition to my collection! πβ¨
02.03.2026 20:41
π 0
π 0
π¬ 0
π 0
The glassy #MeetWithApple in #Warsaw was, as always, extraordinary! β¨
#WWDC26 is almost 3 months away. Todayβs #AppleEvent gave me new energy β‘ to make the most of this time, celebrate current progress π, and prepare for future challenges!πͺ
Canβt wait to see whatβs next! π
02.03.2026 20:41
π 0
π 0
π¬ 1
π 0
Friday! π΄
27.02.2026 22:08
π 0
π 0
π¬ 0
π 0
Yes, exactly. That is why the research is very important. Each new release mobilized to deep dive into novelties.
Now, you have anything under one command, without a reflective study of the content.
27.02.2026 06:53
π 1
π 0
π¬ 1
π 0
The art of self-compromising is extremely important in your private projects. π
You may love smooth code, but when youβre paying yourself with a free time, the most important thing is the results. π
Still, Iβm about to sit down with #Instruments and see how it performs. π
26.02.2026 20:37
π 0
π 0
π¬ 0
π 0
Then the stairs begin. β°οΈ
Should I use #generics or #any keyword? How to describe the #protocol? Is it worth to replace struct with a class. π€
When I hit this, I set a deadline - if I canβt solve it, I take the easiest path and leave a ToDo. ποΈ
#Swift #Developer #iOS #Xcode
26.02.2026 20:36
π 0
π 0
π¬ 1
π 0
Sometimes, I have an idea that seems great - but then the implementation ends up looking tragicβ¦ π«£
I wanted to update the current #Coordinator to provide an easy-to-use #View. In addition, I wanted to pass #Payload, since flow isnβt always independent.βοΈ
#BuildInPublic #Swift
26.02.2026 20:36
π 2
π 0
π¬ 1
π 0
What I really like is having the whole codebase in one dir: #mobile app, #backend, support services, and the legacy - all in one place.
#Claude seems to work better when it understands the whole concept, not just part of the code.
New feature? The #agent has insight everywhere.
25.02.2026 19:34
π 0
π 0
π¬ 0
π 0
It will not teach you how to manage memory, look for erroneous patterns in the handling of threads and why the view in SwiftUI is refreshing too often.
Itβs not a matter of documentation but of experience. With ready answers, the learning curve is flat, which does not happen when you make research.
25.02.2026 13:40
π 2
π 0
π¬ 1
π 0
Unfortunately, a human is lazy by nature, so we will check ready-made answers less often.
The information access curve is changing, but the learning curve suffers from it.
Learning calligraphy will take you a lot longer if you write on the trail even if initially the effects will be ok.
25.02.2026 13:35
π 0
π 0
π¬ 0
π 0
Yeah, I was there tooβ¦ π
25.02.2026 13:33
π 1
π 0
π¬ 0
π 0
π°οΈ I miss the old days sometimes
There was something romantic about discovering solutions yourself. Hours deep in documentation, #StackOverflow, trial and error until breakthrough.
Now? Ask #AI, get an answer immediately.
Anyone else feel this? π
#BuildInPublic #DevDiary #iOS
24.02.2026 15:58
π 5
π 1
π¬ 3
π 0
π Before any code hits the repo, I examine everything
AI-generated code is a starting point, not a finish line. Backend is usually solid. πͺ
The arch might be right, but the details need my touch. #SwiftUI layouts, accessibility, iOS-specific patterns - those need my judgment.
24.02.2026 15:58
π 1
π 1
π¬ 1
π 0
π§ Stage two: Claude Chat β Claude Code
Once the concept is clear, I switch to #Claude Chat for the technical side. Here I'm refining the approach, preparing prompts, getting specific about #architecture.
Next is #ClaudeCode where I am running many fresh sessions per case. π
24.02.2026 15:58
π 2
π 0
π¬ 1
π 0
π My AI workflow starts with ChatGPT
When I'm exploring a new technical challenge or productive case, #ChatGPT is my first stop. Why? It pours more water on ideas.
The goal isnβt perfect code - it helps me plan the whole module and align new ideas with the project environment.
24.02.2026 15:58
π 0
π 0
π¬ 1
π 0
I donβt know if LLMs will actually take away our work. π€
Still, it's not like the #app will write itself. Even a simple search has so many edge cases - Iβve been thinking about this for a while, but no #LLM has nailed it yet. π¦
But I know - from experience. π¨βπ»
#BuildInPublic
20.02.2026 22:34
π 3
π 1
π¬ 0
π 0
Itβs such a trap of prosperity... Man wants more and more...
19.02.2026 22:00
π 0
π 0
π¬ 0
π 0
I noticed today that #AI doesnβt help me finish projects at all.
Instead of closing the scope with specific functions, I add more trifles, refine details, and expand the current flow.
I need to focus on a milestone to finally bring the product to a point where I can publish it.
19.02.2026 22:00
π 0
π 0
π¬ 2
π 0