jwdunne
Joined 16 years ago
Joined 16 years ago
i have no doubt that places were practicing waterfall in the large. people running businesses, both vendor and client, want 'predictable' estimates up front, with a single timeframe, and single quote
but i suspect internally projects followed an iterative process, where designs were refined repeatedly and testing happened early. because you had to
unfortunately, those projects were still judged by a waterfall yardstick, with inflating timescales and bills, giving something for agile to attack
and on first blush, agile, the manifesto, sounds reasonable enough
but, after 30-40 years of practice to reflect upon, agile:
- has some good parts that were already well documented, i.e royce and brooks
- some radical parts of dubious general applicability and benefit
- just enough ambiguity that we have since been arguing what true agile really is
and this is what prevents it from ever really working or being the basis to solidify an engineering field around
it helped us get some of the way there but it won't help us get further and it's time to let it die
I think Proxy _is_ overkill and perhaps expensive for what it is. For a pg install, running pgBouncer isn’t difficult. But I guess that depends on whether you’re authenticating with IAMs, which doesn’t sound trivial with bouncer (it might be).
Unfortunately, it’s taking far too long for Laravel to catch up so parts of its API are a black hole for types.
Especially things like request input, which returns a union of string and array as opposed to using a conditional return type.
You end up with assertion soup every time you touch Laravel so over time the project uses less and less of it.
A well-typed framework and set of libraries would be very nice.
tHiS sHoUlDn’T bE oN hAcKeRnEws