Para Jao retweeted
Interesting post. There is quite a bit of room for applying this today. One problem is that often there is value that is not part of what is measured.
Para Jao retweeted
I would predict that TDD, DDD, RDD, although in newer forms to account for changes in workflow are going to be the real winners in your skillset in a post GenAI world.
Curiously, exactly at that point that many voices are trying to talk them down in favor of rawdogging the code.
Para Jao retweeted
If UK Labour wanted to actually stimulate economic growth, they would introduce a significant wealth tax and redistribute to the poorest. High and persistant inequality is stagnating our economy by shifting it from productive enterprise to rent seeking ->
This quoted post is unavailable.
Para Jao retweeted
How can you use test doubles?
Thank you @consolondon and @parajao for sharing your insights: Test Doubles without Tears.
Watch on Youtube youtube.com/watch?v=cok0L4r4…
Thanks @valentinajemuov, @dmokafa, @oliverzihler & @AlinaLiburkina for organizing.
#tdd #techexcellence
Para Jao retweeted
Tests should couple to behaviours not implementation details
youtu.be/EZ05e7EMOLM?si=zOgn…
youtu.be/IN9lftH0cJc?si=X63b…
Para Jao retweeted
Once upon a time agile was a developer led revolution in how we built software.
Then for reasons, perhaps lost now, it split into software craftsmanship - the dev practices - and scrum.
That was when it died.
We need to make it whole again.
Para Jao retweeted
I am currently convinced that if your product does not need unit tests to maintain its stability then it's worth nothing
It has no technical moat, here today gone tomorrow
Para Jao retweeted
1. If I can’t write test before implementation, I need to find system behavior first.
2. If test name is saying more about HOW but not WHAT system is doing, I need to find system behavior first.
3. If I don’t know system behavior, I need to talk with domain experts first.
Para Jao retweeted
Contemplating writing a LeanPub book on TDD, Ports and Adapters, CQRS (without ES), and 12-Factor. In other words an opinionated view of how to development.
Likely a first version in C# as it’s my most comfortable language but possibly translatable.
Para Jao retweeted
I think is is exemplary of how *not* to deal with LLMs. Instead of thinking of them as being "intelligent" and hence try to make them do heroic zero-shot feats, we should leverage their strengths as dumb next token predictors and let them generate code or sequences of tool interactions.
Why jump through hoops to make the model solve this puzzle directly when it can trivially generate the code that will solve it indirectly.
A::B Prompting Challenge: $10k to prove me wrong!
# CHALLENGE
Develop an AI prompt that solves random 12-token instances of the A::B problem (defined in the quoted tweet), with 90%+ success rate.
# RULES
1. The AI will be given a random instance, inside a <problem/> tag.
2. The AI must end its answer with the correct <solution/>.
3. The AI can use up to 32K tokens to work on the problem.
4. You can choose any public model.
5. Any prompting technique is allowed.
6. Keep it fun! No toxicity, spam or harassment.
# EVALUATION
You must submit your system prompt as a reply to this tweet, in a Gist. I'll test each submission in 50 random 12-token instances of the A::B system. The first to get 45 correct solutions wins the prize, plus the invaluable public recognition of proving me wrong 😅 If nobody solves it, I'll repost the top 3 submissions, so we all learn some new prompting techniques :)
# DETAILS ON GIST
gist.github.com/VictorTaelin…
Para Jao retweeted
Guessing the next word without understanding the meaning of the resulting sentence makes unsupervised LLMs unsuitable for high-stakes tasks. The whole AI bubble is based on convincing investors that one or more of the following is true:
6/
Para Jao retweeted
I wrote this Format dialog back on a rainy Thursday morning at Microsoft in late 1994, I think it was.
We were porting the bajillion lines of code from the Windows95 user interface over to NT, and Format was just one of those areas where WindowsNT was different enough from Windows95 that we had to come up with some custom UI.
I got out a piece of paper and wrote down all the options and choices you could make with respect to formatting a disk, like filesystem, label, cluster size, compression, encryption, and so on.
Then I busted out VC++2.0 and used the Resource Editor to lay out a simple vertical stack of all the choices you had to make, in the approximate order you had to make. It wasn't elegant, but it would do until the elegant UI arrived.
That was some 30 years ago, and the dialog is still my temporary one from that Thursday morning, so be careful about checking in "temporary" solutions!
I also had to decide how much "cluster slack" would be too much, and that wound up constraining the format size of a FAT volume to 32GB. That limit was also an arbitrary choice that morning, and one that has stuck with us as a permanent side effect.
So remember... there are no "temporary" checkins :)
Follow me for more random code musings!
Para Jao retweeted
if you committed this to a codebase i worked in, i would do everything in my power to replace this with a couple asserts and see to it you leave my team
please for the future you do not commit code you don't understand
Para Jao retweeted
The following diagram is literally all Ports & Adapters is (DDD notes because it is from a DDD facing deck only)
Don't believe the vertical slices crowds straw-man description
Para Jao retweeted
I wrote a little blog post on best Rust extensions a while ago. I thought it wouldn't have much traction, so I didn't even share it. Turns out it's the post that gets more visits at the moment 😄 so I'll share it here:
srodrigoroyo.com/best-vs-cod…
#rust #rustlang #vscode #programming
Para Jao retweeted
🤔 In cosa migliorerò dopo Software Crafting Programme @parajao @consolondon?
🤩 L'idea è fornire non soltanto la conoscenza, ma anche un workflow ripetibile e predicibile per la delivery di software di alta qualità e allineato coi valori dei business. open.spotify.com/episode/3tu…
Para Jao retweeted
Perché partecipare a Software Crafting Programme? Ti diamo almeno due buoni motivi, in due tweet diversi...
1️⃣ Per imparare a scrivere software mantenibile e di alta qualità, senza cadere nelle comuni trappole di over engineering
@parajao @consolondon
bit.ly/Software_Crafting_TW
