Date: Thu, 11 Dec 2025 18:17:44 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> To: Sad Clouds <cryintothebluesky@gmail.com> Cc: Lexi Winter <ivy@freebsd.org>, questions@freebsd.org Subject: Re: Trying to understand base system packages Message-ID: <86qzt1aqfb.fsf@ltc.des.dev> In-Reply-To: <20251211123858.9d0291a10688d91ad7a15d52@gmail.com> (Sad Clouds's message of "Thu, 11 Dec 2025 12:38:58 %2B0000") References: <20251205122830.cb88058f193987b47a95a77c@gmail.com> <20251205134510.6fae5caf@dorfdsl.de> <20251205143119.441cc1bd8722345d074a4480@gmail.com> <16e766b9-f442-4cef-a991-c940f6b8182a@gmail.com> <20251207081139.7e2f65b97b4c089ac0add431@gmail.com> <aTkvIvFJHLf4WxUa@amaryllis.le-fay.org> <aTm6mdWQ_nyv21El@rain.cave> <20251210203319.c248921c4e6aca9ba07458ae@gmail.com> <aToOxuaXNTa5LOOP@amaryllis.le-fay.org> <20251211093606.eade25c5f5c65277120d2f6e@gmail.com> <86ecp1cnji.fsf@ltc.des.dev> <20251211112643.c8778646e28c8ce70d6a0ea2@gmail.com> <868qf9cj05.fsf@ltc.des.dev> <20251211123858.9d0291a10688d91ad7a15d52@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sad Clouds <cryintothebluesky@gmail.com> writes: > OK I respect your views, however based on your experience, which > software methodology would you employ for your own projects? And > let's assume these are complex projects which can take 12 months to > complete and you have complete freedom to make your own decisions on > everything. Some variation on Agile, which as Poul-Henning Kamp once pointed out is merely a codification of how F/OSS has always done things. It depends on the size of the team and the relationship with the stakeholders. And yes, like you, I've seen Agile done very, very badly, but I don't blame the method (which has worked well for me) for the shortcomings of the people involved. (I've had to work with a team whose manager constantly demanded detailed documentation for my components while refusing to provide any for their own because “Agile means no documentation”. He also refused to let me speak to his developers because “Agile means I shield my team from distractions” or even relay my questions to them. I eventually cut the Gordian knot by “accidentally” running into his team at lunch.) Note that Agile does not mean you don't write specifications or tests or documentation. It just means you do it repeatedly and continuously and incorporate the lessons you learn from one iteration into your plans for the next. DES -- Dag-Erling Smørgrav - des@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86qzt1aqfb.fsf>