I'm not familiar enough with CSS to understand if you're filing this under bugs with the language / spec or if you mean bugs in developed webpages.
In either case, fixing bugs would fall under the support aspect of what they listed. The full design, development, deploy stages would also fall under that and may be used in various amounts of formality when dealing with bugs.
There is an engineering design process [1] that anyone can learn about and take some useful ideas from. Obviously adapt what's relevant to your needs and discard the overly process or paperwork heavy details that may not be suitable.
There are SDLCs [2] and other software specific IEEE standards that have been developed [3]. If you've been in tech long enough, you've probably figured these out on your own, or some approximation to them, and you may have even come up with your own name for aspects of it. I've seen "metaprogramming" used a number of times on HN to describe aspects of the planning, analysis, and design stages of engineering design.
There definitely are things to be learned by looking at other fields, and I don't think software can claim absolutely zero overlap with other fields. It's not 100% and there are unique constraints, but it's not zero and throw the baby out with the bathwater so to speak.
In either case, fixing bugs would fall under the support aspect of what they listed. The full design, development, deploy stages would also fall under that and may be used in various amounts of formality when dealing with bugs.
There is an engineering design process [1] that anyone can learn about and take some useful ideas from. Obviously adapt what's relevant to your needs and discard the overly process or paperwork heavy details that may not be suitable.
There are SDLCs [2] and other software specific IEEE standards that have been developed [3]. If you've been in tech long enough, you've probably figured these out on your own, or some approximation to them, and you may have even come up with your own name for aspects of it. I've seen "metaprogramming" used a number of times on HN to describe aspects of the planning, analysis, and design stages of engineering design.
There definitely are things to be learned by looking at other fields, and I don't think software can claim absolutely zero overlap with other fields. It's not 100% and there are unique constraints, but it's not zero and throw the baby out with the bathwater so to speak.
[1] https://en.wikipedia.org/wiki/Engineering_design_process
[2] https://en.wikipedia.org/wiki/Systems_development_life_cycle
[3] https://en.wikipedia.org/wiki/ISO/IEC_12207