The Magic of the Most Minimal HTML Possible (and Why We Don’t Make Use of It), by @j9t [@frontenddogma]:
The Magic of the Most Minimal HTML Possible (and Why We Don’t Make Use of It), by @j9t [@frontenddogma]:
Seeking an Answer: Why Can’t HTML Alone Do Includes?, by @chriscoyier (@frontendmasters.com):
https://frontendmasters.com/blog/seeking-an-answer-why-cant-html-alone-do-includes/
Unlocking 7 Hidden Benefits Through Web Site Redesign, by @uxmatters.bsky.social:
Holy crap! I just noticed we're up to 130 unit test suites in @pidgin 3 now! Compare that to the 7 suites we have in Pidgin 2!
This is what we've been talking about when we've been saying that we're making the code easier to maintain. The code has been reworked so that we can actually unit test way more of it and we will continue to add more tests as we move forward!
#Development #Techniques
More readable JavaScript with named parameters · “Named parameters can drastically improve your code.” https://ilo.im/16211p
_____
#Programming #Coding #JavaScript #Functions #Readability #Maintainability #WebDev #Frontend #Backend
...documentation. In other words, it should be "clean" code that looks like it was written by someone who cares. How do you tell? Just ask your colleagues...
So, what do you do to write code that _doesn't_ need an explanation?
@landley @dalias I mean, isn't the whole point of #Linux being written in #C to have #ReadableSource that is #maintainable?
@bagder same reason for #Linux I guess and same reason why I do all the #OS1337 code in #bash with only .config makefiles where needed:
Readable and thus easy to #audit code allows for #transparency, which is vital for #maintainability and #security...
After all, mistakes do happen and I'd rather have it easy find and fix than optimize every bit at the cost of unmaintainable code.
If you're not making an effort to ensure #maintainability, #repairability, #reusability and #durability of new things when we're ramming steadily into the "find out" of the "fuck around & find out" situation with environmental and ecological abuse, you're either irresponsible or malicious.
It is inexcusable to make #EWaste (and most other waste) now. It never was excusable, but the reasons why hadn't yet made themselves blatantly obvious to all observers. Now they have.
@atomicpoet
1 Historically without #internationaltreaty for this, preservation is only via #emulators, mostly for conservartos and researchers, but not for original owners.
2 Most practical resources I know, post other useful ones!
https://mastodon.social/@teixi/109775436502300209
2 Call for #medicaldevice #maintainability #reparability new #InternationalLaw in order to enforce #righttorepair via #escrow assurance to open all things.
Yet also applies to any devices before going into the market:
https://mastodon.social/@teixi/109773861523696576
It's really cool to be getting the question: "Why choose #RIFE2 over other popular frameworks?" already. So I wrote up a page that hopefully answers that: https://github.com/gbevin/rife2/wiki/Why-RIFE2
What are good proxy #metrics to measure #maintainability of #code?
* Time to implement new features
* Time push fixes to production
* Release frequency
* Number of logins to production servers/containers
* Onboarding time of new team members
* WTFs per minute
I am looking for inspiration.
It's really hard to stick with #Firefox with all that featuritis where stuff gets integrated which should be kept separate for #security, #performance, #maintainability and also #usability reasons.
However, we still need to use FF because of https://contrachrome.com/