News for hackers. Stuff that matters.
Re:State of the Common Lisp ecosystem, 2020 by p_l on Tuesday February 09, 2021 @01:25PM (#26080874)
A lot of Common Lisp code that ends up opensourced is either 80% solutions for things that were necessary for some project (sometimes commercial), and IMO the rare cases where things really got polished - they got polished later on with intent to publish.

On the job code, whether lisp or not lisp... I'm more used to managers preventing writing anything more complete or documented, except for once in few months forcing everyone to write BS low-quality docs because "documentation" is a line item on the contract.

My pleas to set aside time to document and polish things are usually ignored, my pleas for a technical writer on staff to help us keep docs current and well written have never been listened to so far.

Re:State of the Common Lisp ecosystem, 2020 by brundolf on Tuesday February 09, 2021 @04:40PM (#26082692)
My own anecdote is that I've never worked at a company where code quality was chronically devalued; that's only ever been a temporary state of affairs for a specific push, after which time is made available to pay down some of the debt

We're both speaking from limited sets of experiences, and neither is likely to be representative of the whole industry