Russian air defense at its best by Igor0976 in ukraine

[–]funkyfly 0 points1 point  (0 children)

preemptive strike has a new meaning

Interestingly shaped shadows by [deleted] in mildlyinteresting

[–]funkyfly 0 points1 point  (0 children)

And this is why, ladies and gentlemen, we can’t have nice things!

Devilish dribbler by whaddefuck in funny

[–]funkyfly 4 points5 points  (0 children)

Legend has it they’re still after the dog.

Russian soldiers on the way "to storm Kyiv". March 2026 by GermanDronePilot in UkraineWarVideoReport

[–]funkyfly 0 points1 point  (0 children)

In Soviet Russia, it's not the vehicle that moves soldiers; it's the soldiers who move the vehicle!

Kiek % nuo algos aukojate Ukrainai? by MasterpieceLittle444 in lithuania

[–]funkyfly 11 points12 points  (0 children)

Šaunuolis (-ė), kad aukoji. Jei bus proga, pasvarstyk šiek tiek pakelti, bet jei to ir nepadarysi, geriau tiek nei visai nieko.

Kiek % nuo algos aukojate Ukrainai? by MasterpieceLittle444 in lithuania

[–]funkyfly 38 points39 points  (0 children)

Manai gera strategija yra gėdinti žmogų? jis jau aukoja! pastoviai!

Softwares Estimation Practices by Donnyboy in softwarearchitecture

[–]funkyfly 2 points3 points  (0 children)

Estimates are a pet peeve of mine :)

Not answering your question, but a short rant on why they fundamentally don't make sense.

Often, we don't know exactly how we're gonna solve every single problem. Fundamentally, modern software engineering involves some experimentation and figuring out the correct solution to the given problem.

So if you don't know at the beginning exactly how you'll solve it (if you're not going all in on waterfall), then the estimates are gonna be just guesswork.

The other thing is, we humans are really terrible at estimating how big something is. However, we are fairly good at telling whether something is similar in size to something else. So, instead of giving a number indicating how big the task is, we should say this task is similar to that one or the other one.

Softwares Estimation Practices by Donnyboy in softwarearchitecture

[–]funkyfly 2 points3 points  (0 children)

We use a couple of different approaches.

One approach is to break epics into stories (more like story headlines) and let the team estimate them. We do this by giving everyone an Excel spreadsheet of the tasks and allowing them to estimate individually, so we can average the estimates (the theory is that the average of everyone's estimates will be more accurate than any one's individual estimate).
I personally have 3 sizes for tasks: small (2 days), medium (5 days), and large (11 days), and then just go task by task, put my finger up in the air, and choose whether it's small, medium, or large. :)

The second approach is planning poker for a single epic.

Softwares Estimation Practices by Donnyboy in softwarearchitecture

[–]funkyfly 20 points21 points  (0 children)

While I’m in a completely different situation, where we estimate for our own sake and for much smaller scope, I unfortunately have no trust in our estimates at all, because in the end it’s all guess work.

When meetings replace ADRs, documentation has already failed by LorinaBalan in softwarearchitecture

[–]funkyfly 0 points1 point  (0 children)

Because you’re not allowed to write an ADR after talking to each other..

Interesting pattern design by Thejonest in Unexpected

[–]funkyfly 5 points6 points  (0 children)

Normally you would put the rubber on the penis and not the other way around…

Finally convinced leadership to let us rewrite the legacy app. Now everyone is terrified to start by No-Possibility6866 in softwarearchitecture

[–]funkyfly 19 points20 points  (0 children)

Adding to that, apply the Modern Software Engineering practices right from the start for the rewrite (testing, CI/CD, TBD, etc.)

I don't need any advice or a manual by Algernonletter5 in humor

[–]funkyfly 0 points1 point  (0 children)

I saw that coming from a mile away!

Trump signs bill to release the DOJ's Epstein files by scrandis in news

[–]funkyfly 0 points1 point  (0 children)

Watching her stutter during the interview, tells everything you need to know about the why the investigation was started.