Enver Bral (@EnverBral) header
Enver Bral (@EnverBral) profile picture

I like to solve problems. Sometimes that involves writing code. A lot of times that involves people.

Belgium
Joined January 2015
Photo by Enver Bral (@EnverBral)Photo by Enver Bral (@EnverBral)Photo by Enver Bral (@EnverBral)Photo by Enver Bral (@EnverBral)Photo by Enver Bral (@EnverBral)Photo by Enver Bral (@EnverBral)Photo by Enver Bral (@EnverBral)
You sometimes need a consultant to come in and say the same thing that employees have been saying for years before change takes place. I know it's frustrating, but don't fight it. Be glad you're now getting the support you wanted and help steer it in the right direction.
23
In this latest episode of the Mob Mentality Show, we dive into a challenge faced by many mobbers: the varying speeds of team members youtu.be/MnMHX5d_Mdc open.spotify.com/episode/2Ki… @ChristophLucian #MobProgramming
1
2
1
3
1,016
I sometimes feel like I’m doing software wrong. Everyone else seems to be shipping features super fast but it takes me months to get anything I want done in my own work.
15
1
33
6,391
2024: New text editors are being developed which boot up X times faster than their predecessors. They also have 0 support for automated refactorings, some of which were described by Martin Fowler back in 1999. Does a quick boot up time really make us that much more productive?
3
2
454
I just got back from @SoCraTes_BE 2023 and can't remember when I last had this much fun at a conference. If you've never been to an unconference, I highly recommend giving it a try.
3
5
283
In an experienced mob, would you generally rotate the navigator when the timer runs out? I've always assumed you do, but never played with only rotating the driver. Would love to hear your experience, @mob__mentality
4
1
2
819
If the problem is too big, find a way to make it smaller
2
112
But, hey, Java programmers have 10,001 annotations to make bad design much easier and faster to accomplish. Some annotations actually do nothing except make said programmers feel better because they can annotate one more thing. xitter.cf/swcraftsman/status/169…
Worrying about the resistence against DDD I was faced within Java community, I started to read @VaughnVernon 's book, hoping to find answers on how to push my teamates into the right direction. Seems there's nothing new under the sun since 12 years...
7
9
2
74
20,245
Software teams should improve and build their own tools if they have a bad dev experience. No need to ask anyone for permission. (Just don't go off building a general purpose framework)
55
grugbrain.dev/ contains surprisingly sound advice Complexity very, very bad
41
Running software in "maintenance mode" is never free. If your software is used long enough, at some point something will change - OS updates, cloud provider EOLing a service, ... - which forces someone to make changes to the software to keep it running.
44
It's as if transaction script became a bad word. Simplistic data models with transaction scripts are a good solution for superficial logic (as mentioned). Don't go down trying to make aggregates because you want to create an object model hierarchy with useless set methods.
. @UdiDahan reminds what we tend to forget: the domain model pattern should be used where it is really needed. Simpler solutions work better for simpler functionalities #NDCOslo Ps You can read more about it in the “Design Heuristics” chapter of “🐒 Learning Domain-Driven Design”
1
7
2,791
Enver Bral retweeted
So that AWS piece tells more about failure to understand what a microservice is, than anything else. There is one microservice in play here: Audio/Video Monitoring Service. That is the sub-domain being automated (and the bounded context) primevideotech.com/video-str… 1/
3
24
7
114
37,008
I just read Valve's Handbook for new employees and found it quite an interesting read. It provides some insight and guidance into how a flat company structure can work, but also doesn't shy away from pointing out some of the downsides.
1
2
78
Knowledge work is mostly invisible. The work might result in visible artifacts such as documentation or code, but the actual work that led to those artifacts - thinking - is not.
1
86
For me this has two consequences: 1. Don't judge the amount of work done by looking at the output. The output and the effort it took to get to that output cannot be mapped one-to-one. 2. Visualisation is extremely important: it forces us to make some of our thinking visible.
61
Recently learned: Don't mistake the boundaries around cross-functional teams as silos that should never be broken. If team A is blocked by team B because they need X, but B is busy doing Y, then A could help B with Y, even if Y has nothing to do with A.
4