MorganFR wrote in a comment: "you're probably looking for disband or one of its synonyms."
Disband — M-W
transitive verb: to break up the organization of : dissolve
intransitive verb: to break up as an organization : disperse
"They've decided to disband the club."
"The members of the organization have decided to disband."
There is a programming joke, 'It's not a bug, it's a feature' and 'If you can not fix a bug, try to prove it's a feature'
But grammatically, 'bug' is a slang for 'error', and the opposite for 'error' in programming code is 'validity', and debugging software naming is 'debugger' or 'validation software'.
The error messages may state 'Invalid code',...
The process of taking a well-designed piece of code and, through a series of small, reversible changes, making it completely unmaintainable by anyone except yourself.
Bit tongue in cheek, but as you mentioned in the original post, people don't (normally) intentionally make code worse!
Before there were software bugs and software programs that needed to be de-bugged, the term existed and applied to defects or flaws in circuits, machines or operations.
From the Index to Radio for the Year 1937:
There can be no doubt but that many new and simple noise silencers will appear, both of the amplitude limiting and the "silence punch" types. ...
As an example of fairly standard usage in the software and technology sectors, a program or system will be described as having a number of known issues. These will typically by prioritised and addressed in a planned way. However, areas of a product that are not affected, can continue to be used without any issue.
Examples of common usage ...
The idea that software degrades over time is known as software rot (or, slightly less specifically, "bit rot"). There are two main variations. The first is that software that is not being maintained gradually degrades over time as the environment around the software changes. For example, upgrading to a new version of an operating system might make an ...
Typical uses are to: dissolve parliament, dissolve a partnership, dissolve a marriage. "break up" is given as its synonym.
Part of the definition from Merriam-Webster:
1a : to cause to disperse or disappear : destroy (do not dissolve
and deface the laws of ...
I would agree with the other answers. "bugged" is incorrect usage. The standard American programming terminology is that the "software is buggy" or "has bugs" and this has been true since I began programming around 1980.
Generally speaking reactions would apply here and is used on the messaging platform Slack.
Whether it's a like, a dislike, a thumbs up, a heart or a pizza emoji, the users are reacting to the post, so it makes sense to record these as reactions.
In computing circles, we often refer to numbers like 10K, 24M, 120G as being human-readable or humanized numbers. This is often in the context of byte counts, which can get notoriously unwieldy with modern storage sizes (e.g. saying I have 323416563175 bytes free on my computer), though I have seen it applied to other contexts as well.
For example, the man ...
I have mostly seen it from non-native speakers, or children (approximately under 14) on the forums of Blizzard games and Plex. I agree with all other posters that buggy is the correct adjective. There is no verbal form. See the buggy/bugged software n-gram.
The prevalent usage is "the function has a bug" or "the function is buggy".
There is a very subtle, but important difference that is highlighted when you look at the word debugging. Debugging is the process of intentionally tracking down and removing bugs. Bugging would be the opposite, intentionally placing bugs.
This makes sense - if a room is bugged, ...
1.1 (of a gathering or collective) disband
In your context, you might say
After Tim left, management decided to break up the team
Also consider 'split':
After Tim left, management decided to split the team
If we want a well-known word that appears in standard dictionaries, and already has a domain-specific definition which applies specifically to software, I would recommend you use obfuscating, which is defined in the software discipline as something like "the process of making code harder for humans to understand." This can be done simply by removing relevant ...
Most appropriate expression seems to be "unintended feature".
A bug is unintended, and is bad for users.
A feature is good for users, but, in this case, it was unintended.
Web Search also throws a lot of results for this expression, so it seems to be widely accepted.
After some more thoughts on this, I have this grid:
| - | unintended | ...
I will reiterate what Bjarne Stroustrup has to say:
"char" is usually pronounced "tchar", not "kar". This may seem illogical because "character" is pronounced "ka-rak-ter", but nobody ever accused English pronunciation (not "pronounciation" :-) and spelling of being logical.
The best word for something that cannot be split in a programming context is atomic.
This is used a lot, and is essential for interruptible programming. For example, in a signal handler you should only touch variables of type sig_atomic_t and storage class volatile, as explained here.
I don't believe there is a specific term which applies only to numbers, but we can say such numbers are abbreviated.
For example, the University of North Carolina says of such numeric suffixes:
K: an informal abbreviation for one thousand used in expressions where the unit is understood, such as "10K run" (10 kilometers) or "700K disk" (...
I'd describe that software as buggy. As a software developer, we often encounter buggy code/software/etc. It usually works just fine except for a few use cases. In my experience this is common parlance among developers.
The website works great, but for some reason you can't login if your e-mail address has more than 20 characters. It's a little buggy.
The words like that will try to follow the current word-form rules in similar words. (to trap - trapping). The word "grep" is already in some dictionaries and it follows this theory:
verb (greps, grepping, grepped) [with object]:
Search for (a string of characters) using grep.
While I agree with others that 'buggy' is far more common usage, I do hear the term 'bugged' used to describe code from time to time. Additionally, it is usually from professional software engineers or developers who are native speakers of American English that I hear the term used.
Usually, I hear 'bugged' in reference to code that has (or had) a ...