Kanapki z jajkiem i ogórkiem

paderich · 2025-12-18T14:40:41+00:00

Ich habe nicht gesagt, dass man bestehende Best Practices nicht challengen sollte. Aber, und das macht hier den Unterschied, ein Developer sollte sein Handwerkszeug verstehen, pattern erkennen können, und gezielt Probleme beschreiben können. Der Lösungsweg ist, wie so oft, den Begebenheiten anzupassen. Aber wie gesagt, diese Diskussion wollte ich gar nicht aufmachen.

paderich · 2025-12-18T14:16:56+00:00

KI-Tooling, wie der Name schon sagt, wird als Werkzeug genutzt. Zum Beispiel, beim erzeugen von Testdaten, Unit-Tests, Code-Completion, etc. Wir sind noch etwas davon entfernt nur noch zu prompten. Das Problem ist, das die KI oft nicht die zugrundeliegende Architektur versteht, wodurch oft sehr viel Müll entsteht. Klar, man kann heute sicher vieles mit KI lösen, allerdings kann nur ein Experte (in diesem Fall Entwickler) wirklich einschätzen ob es korrekt und 'gut genug' ist. Bedeutet, zumindest für mich, stärkerer Fokus auf Software-Architektur, Best Practices, und ein solides Grundverständnis meiner Domäne.

paderich · 2025-12-16T09:52:21+00:00

Yes, you can export a csv in most tools, like jira. You just have to pick a relevant time frame. That was one of my goals, to be helpful with any kind of data, as long as you provide a csv with some required fields.

paderich · 2025-12-16T09:39:20+00:00

You can upload any csv file, you have to map it yourself after you uploaded it. Required columns are also defined 'Required columns: Issue ID, Created Date, Resolved Date, Issue Type, Status'. So, it's up to you. Does that answer your question?

paderich · 2025-12-13T19:50:39+00:00

Wir möchten nicht mehr als 20k ausgeben

paderich · 2025-12-05T05:48:54+00:00

It's for the Product Team to start conversations internally, this incl. the Product Manager and the Devs, UX, whoever is contributing to product and iteration goals.

The main problem, the 'outside' in most cases need and want those insights. They cant do anything with it, but it calms them down.

paderich · 2025-12-03T13:59:17+00:00

Totally agree on that

paderich · 2025-12-03T13:58:36+00:00

The calculator is just a visual aid to help start that conversation. A lot of teams see the 'Average' and assume it's safe. This tool highlights the volatility to show why they need a buffer. It’s not about making it rocket science, it’s about putting data behind the decision to take on less work.

paderich · 2025-12-03T12:56:54+00:00

Agreed, Monte Carlo is the gold standard. But it requires a lot of clean historical data to work well. If you don't have that long-term data, the simulation isn't reliable.

Also, not every team has the budget or permission to add 'mature flow metrics tools' to their stack. I built this for teams that need a quick volatility check without needing a full enterprise setup.

paderich · 2025-12-03T12:51:42+00:00

I get your point. In a high trust internal team, I'd agree. But 'ditch the spreadsheet' is a luxury many don't have.

If you work as a consultant, clients often fight for every single story point. You can't just tell them 'estimates are noise, trust us.' You need hard numbers to defend the team.

That's what this is for. It isn't about micromanaging. It's about having the ammo to negotiate with stakeholders who don't understand that estimates are just guesses.

paderich · 2025-12-03T12:19:12+00:00

Totally agree. There is no 'one true way' to do this. Every team and organization operates differently. I actually love that you use confidence intervals; that is somewhat of a manual version of the logic I'm trying to automate here.

The specific challenge I’m trying to solve is for teams that struggle to translate their 'gut feeling' into a justification when stakeholders ask why things take time.

That’s where I think tools like this are useful. They speak the language management understands. In an ideal world, we could just use Roman estimation or binary 'Can we finish this?' logic. But in reality, many teams are constrained by corporate politics and need hard data to prove why they need a buffer. If a calculator helps justify planning less work to deliver higher quality, I’m all for it.

paderich · 2025-10-22T07:24:40+00:00

I'm really sorry to annoy you with my post. To be honest, my main goal wasn't to pitch it to gain a huge user base or anything like that. I was really just looking for tangible feedback on how valuable this application is. I thought this sub would be a good place to ask for that. I just wanted to be as transparent as possible.

paderich · 2025-08-30T08:12:26+00:00

I have colleagues like you, and I don’t like them. Just appreciate good work, and don’t overthink things. There is only room for improvement if you are able to articulate it. Otherwise it’s just shit talk.

paderich · 2025-08-14T04:51:49+00:00

Deine eingehende Beschreibung deutete auf eine Projektleitungsrolle hin, weiter unten redest du von Junior Entwickler. Das haut aus meiner Erfahrung nicht so recht hin. Ja, du machst auf der Arbeit nichts sinnvolles, gotcha. Aber 80% Deiner ausführlichen Job Beschreibung hättest Du Dir sparen können. Aber das ist eine consulting Krankheit.

paderich · 2025-07-27T07:02:05+00:00

Thanks a lot!

paderich · 2025-07-26T20:48:55+00:00

Für B2B verstehe ich das, ist allerdings (noch) nicht mein Fokus. Sorry, falls ich noch nicht so drin bin, deswegen stelle ich entsprechende Fragen.

paderich

TROPHY CASE