nine psch: or /win 14 08:05
WRT development methodologies: scrum style meetings instead of design and on the spot decomposition works quite well for low tech user facing code where the hardest part usually is finding out what the user actually needs. 08:12
Waterfall type development falls down hard on those but works much better for technically difficult challenges where you really have to think a lot before starting to code. 08:13
stmuk I've not seen scrum work particularly well for maintaining legacy code either 09:50
new websites work better 09:51
brrt nine: i agree... it's just that, imho, 'working well for technically non-challenging projects' is a very low bar to meet for a /technical/ project method 10:40
brrt ... wtf 10:47
i've been having nothing but problem with all sorts of apps on fedora lately
*problems
turns out, my session is accidentally on wayland rather than X
focus changes, qt apps, etc, all of these broken 10:48
mother of ...
now i change it back to X, and *everything works again*
arnsholt =D 10:53
brrt it's less funny from this end 10:54
:-P
i've been *so* frustrated
arnsholt I can imagine! 11:00
I've had some X troubles in general, but that's been due to my weird WM (XMonad) not that kind of shenanigans 11:01
nine Oh technically non-challenging can still mean challenging :) And probably most software development projects fall into that category 12:09
brrt: also I actually see itbas a good sign that it took you a while to notice that you're on Wayland :) 12:10
brrt nine: that is also true (about nontechnical challenges) 12:56

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!