Recent searches
Search options
#softwaredesign
For me, one of the best definitions of Test-Driven Development comes from the paper "Mock Roles, Not Objects" by Steve Freeman, Nat Pryce, Tim Mackinnon, Joe Walnes.
http://jmock.org/oopsla2004.pdf
Every Service Should Have a Killswitch, by (not on Mastodon or Bluesky):
Let’s say you’ve just finished a major software project that took a year to complete. How long would it take you to write the exact same system again?
Probably no more than a third. My latest blog post discusses why.
The GOTO bookclub podcast of my conversation with Gregor Hohpe about #CommunicationPatterns is now out.
We talk about technical communication, from visuals to knowledge, and writing to distributed working.
Find it in all the places you usually find podcasts 
or here: https://gotopia.tech/podcast?utm_source=Mastodon&utm_medium=Social&utm_campaign=professional&id=fvhcT8xDz9
From Overview and Status of DoradoLisp under "Linguistic uniformity" on page 2:
An important sociological benefit of having a programming system described in the language it implements is that the system's implementors and users share the same culture.
Why does your code feel off? Hynek reveals the hidden forces that shape our architecture decisions. A must-read for better design choices.
#PythonDev #SoftwareDesign #ArchitecturePatterns https://hynek.me/talks/design-pressure/
You’re Misunderstanding DDD in Angular (and Frontend), by @ducin.dev (@danielglejzner.bsky.social):
https://www.angularspace.com/youre-misunderstanding-ddd-in-angular-and-frontend/
Mike Amundsen Rebecca’s Web – Traces, tracks, trails, and paths https://buff.ly/Jakixga
"This essay explores ways we can grow as designers by becoming more aware of our heuristics, acknowledging the inherent uncertainty in the design process, and learning better ways to articulate and share our heuristics with each other."
"Good software is like a good tool: invisible when it works well." – Unknown
#SoftwareDesign #DevPhilosophy
For me this approach of writing tests after the production code add too much overhead to the development process. I like to prevent such unnecessary headaches. That's why I find Test-Driven Development to be the most effective approach to developing software.
Is there anyone out there who actually understands AI? How to design & train one? How & why they work? How & why they are different from many software projects? What they are FOR?
There's so much #BS, and almost no actual understanding. This is scary...
Test-Driven Development can be considered as reducing your WIP (Work-In-Progress) at a microlevel. By focusing on writing just enough code to make a failing test pass, refactoring what you added and push to source control, we minimise the amount of unexecuted code (= WIP). Limiting WIP is essential for fast software delivery.
For over two years now I've been working on the revival of a community calendar that was built in the heady days of the sharing economy before Uber and friends extracted every ounce of community goodwill in their thurst for profit.
A FOSS self hosted community ecosystem calendar (like say one for the local indie band scene) seems like a natural fit for the fediverse.
I've been unpacking some ideas for how this might work in the discussions on the code repo.
Would love folks to give it a read and give any feedback.
New intro now I am retired...
Looking to get into some #Indie #GameDev now I have time. Want to write the games I wanted to write all along: #Roguelike #Roguelite #ProceduralContent...
Also available to help other people with projects/personal development... Commercial or unpaid, drop me a message, the worst can happen is I don't know or am too busy.
Skills: #SoftwareEngineering #SoftwareDesign
#C++ #Teamwork, #C++, #Online
Carl Svensson on why desktop user interfaces haven't evolved much:
"To me, trying to reinvent the desktop experience feels a bit like complaining about steering wheels in cars."
Only repeated refactoring combined with a growing understanding of the problem and its potential solutions will lead to simple code, design, and architectures.
So "Make it simple, stupid" (MISS)
#Architecture #SoftwareDesign #Code
(2/2)
Great Software Design Looks Underwhelming, by @sjgoedecke@x.com:
Server-centric design is almost always the wrong architecture to use for anything that is not strictly and invariably hierarchical (and even then, a *lot* of cases can do with message-centric and/or content-addressed distributed protocols).
#SoftwareDesign #Software #Servers #Protocols #Architecture #DoingItWrong
Once again, GMail is helpfully shepherding me to overcommit myself by *only* providing 'Yes' suggestions when someone asks me to do a thing.
But, here's a secret: I already know many good ways to say 'Yes' to things! Those words already flow out of my fingers very easily.
I would find it far, *far* more helpful and labor-saving if Google would provide a variety of starting points to kindly/politely say 'No' to a request.
