Alex Shkurko retweeted
I'm suspicious of the idea that we solve problems w/ insight. I work collaboratively w/ customers to iteratively arrive at good solutions. Customers don't know—WE don't know— what they are. It's an iterative process, not a stroke of "insight." It's about feedback & small steps.
Alex Shkurko retweeted
Наші союзники не надавали Україні ATACMS та нові танки, щоб «не йти на ескалацію» і не провокувати до неї росію.
Але росія сама йде на ескалацію. І більш потужна зброя для України це необхідність. Без цього не буде безпеки у всій Європі.
Alex Shkurko retweeted
📅 Wednesday, September 21st, 6:00 PM CET
Update your notion of secure #softwaredevelopment with @julepka during Simple Security & Compliance online event. Julia will cover basic #security principles, best practices, and current trends.
Watch live: youtu.be/jItVqWX_Dx4 👈
Alex Shkurko retweeted
Curious about how the #eCommerce horizon changed over the course of last year?🤔
Check out the insights and findings from Atwix CEO @slkra, where he compares the 2022 and 2021 editions of the Gartner Magic Quadrant for Digital Commerce.
atwix.com/ecommerce/gartner-…
Alex Shkurko retweeted
Дружок Стрємоусова вештається Києвом, обурюється метолшукачам на вокзалі та інсталяціям про російсько-українську війну.
Маю відчуття, що скоро він буде обурюватись інсталяціям у лікарні або в камері.
Alex Shkurko retweeted
🐘 Can you believe I didn’t know that PHP has a backtick operator?
Anything between `` will be executed like shell_exec and returned 🤯
Docs: php.net/manual/en/language.o…
Alex Shkurko retweeted
Automatic retries & idempotent APIs at AWS
aws.amazon.com/builders-libr…
Alex Shkurko retweeted
There is NO SUCH THING as a "technical *user* story." A user story is a story that your user tells to you. It describes your user's work, not yours. "Story" is not a code word for "some random programmer task." Tech is an implementation detail for a story, not itself a story.
Alex Shkurko retweeted
Don't be customer-driven.
Be customer-informed.
Don't be data-driven.
Be data-informed.
If you're going to be driven by anything, make it outcomes 🎯
Alex Shkurko retweeted
There are better ways to achieve these results than estimation, IMO. Discussing how to make a story smaller is typically _vastly_ more useful than discussing what size it is or what's involved with implementing it. There's some value in estimating, but there's more value in not.
Replying to @allenholub
Estimating story sizes is a fabulous thing from a brain&social perspective. It allows to connect different parts of the brain and make those connections&conclusions explicit. It also increases information flow between peers (social density),improving perspectives&shared knowledge
Alex Shkurko retweeted
You are totally replaceable at work.
You are not replaceable at home.
Home is your real life, keep that perspective always.
Don't forget
Alex Shkurko retweeted
If you use 2-week Sprints, work only on stories decided in planning, & release only once at the end of a Sprint, the minimum time to get a change into a user's hands will be ~1 month. Not acceptable. We can argue about whether that's "bad Scrum," but a lot of shops work that way.
A perfect example of how Agile _should_ work: I use @odrive instead of Dropbox. Yesterday, I posted a comment on the tech-support board asking for a trivial change that would make my life much better. 1/3
Alex Shkurko retweeted
A huge amount of mental energy goes into ppl trying to justify/rationalize/inject waterfall thinking into Agile. Estimates, up-front architecture & other rigid plans, tactical roadmaps—all waterfall artifacts that hinder, not help. That energy would be better spent working.
Alex Shkurko retweeted
Just blogged: "Simple Solutions 1 - Active Record versus Data Mapper" matthiasnoback.nl/2022/08/si…
Alex Shkurko retweeted
Me and @ericnormand are preparing a live video AMA session to discuss the synergy between Grokking Simplicity and Data-Oriented Programming.
What would be a good title for the session?
Alex Shkurko retweeted
Educating a team slows you down for a week or two. Not educating the team slows you down forever. Time spent in learning is never wasted.
Alex Shkurko retweeted
The idea of a "full stack developer" is an insane fantasy, given the complexity of modern software. That's why we have full-stack *teams.* Every skill needed to get an idea into our customers hands is represented *on the team* by at least 2 ppl, & everybody teaches everybody else
Alex Shkurko retweeted
Take a deep dive into the best practices of using the #QualityPatchesTool or QPT with different Magento platforms!
Check out the new blog post by @AlexFirster, Tech Lead at Atwix👇
Feel free to let us know if it was helpful for you💪!
atwix.com/magento/quality-pa…




















