Sometimes we come together, we talk, we share our struggles, nobody has a really satisfying answer, but at least we're not alone... and maybe one helpful idea is enough for today.
https://office-hours.jbrains.ca
=> More informations about this toot | View the thread
TIL about gron and jless, which both seem indispensable to those who consume JSON objects.
https://github.com/tomnomnom/gron
https://jless.io/
=> More informations about this toot | View the thread
One very common impediment to building software incrementally lies entirely within your control: a gnawing feeling that the next tiny step you want to make isn't worth it.
It is. Go ahead.
Feel silly and do it anyway. If it's what you need to do to move forward, then you're not wasting time.
=> More informations about this toot | View the thread
I am thinking about publishing a video series in 2025. My working title is "It Depends" and my slogan is this:
I don't know The Right You and neither do you.
Do you have any debates, topics, or questions that you'd like to see me talk about in such a video series? I have in mind 2-10 minutes each.
=> More informations about this toot | View the thread
What is this "Saff Squeeze"? Can I use it even without automated tests?
https://blog.thecodewhisperer.com/permalink/saff-squeeze-example-1
=> More informations about this toot | View the thread
Are you tired of the torrent of blame and guilt and shame in your feeds? Many of the folks posting are well-meaning and trying to help you, but the implied criticism often gets in the way of benefiting from their advice.
I offer an alternative. It's not free, but then you get what you pay for.
https://experience.jbrains.ca
=> More informations about this toot | View the thread
A respected friend is involved in this event, which you might find interesting.
And it's free!
And it's going on now!
https://conference-registration.unlimitedagility.com/
=> More informations about this toot | View the thread
Even when we're struggling with manual tests and printfs, we can stay on task more easily with a single goal.
And, of course, I help my client by letting them run wild through the forest while I carefully write things down, since I have no idea what might be relevant in the next 30 minutes. And, for a few moments at the end, when we reflect, we reflect on the value of writing things done.
And if they write a few more things down next time, then I feel like I've helped.
https://experience.jbrains.ca
=> More informations about this toot | View the thread
Today, we struggled to write even a single automated test, but we used the Saff Squeeze, anyway. And it was hard to stay on task, because we're looking at all this production code and noticing all these things that we don't like... but the Saff Squeeze gives us two simple goals:
=> More informations about this toot | View the thread
When you work on code not familiar to you, then you are more easily confused, spend more time struggling to figure things out, and feel more stress from experiencing things that shouldn't happen and situations that feel like they take you away from your goals.
In those moments, precise technique creates safety.
=> More informations about this toot | View the thread
In a 1-on-1 session with a client, I'm reminded about when precise technique becomes important.
When you work on code that feels familiar to you, then you can follow your intuition more often, allow yourself to be distracted more, and generally this will not hurt you as much. This happens because you see more of what you expect.
=> More informations about this toot | View the thread
In 1-on-1 sessions with programmer clients, we routinely start with a programming task and end up working on two things:
Today, we only practised number 2, but we did that a lot.
=> More informations about this toot | View the thread
Why refactor? To reduce volatility in the marginal cost of features.
We can see this as a socially acceptable way of saying "to express love", especially in a job context.
What would happen if we embraced this idea? Why don't you embrace this idea now? What obstacles stand in your path?
=> More informations about this toot | View the thread
Module load paths need to be relative to the directory in which one executes the command, not relative to the "main" file that that command interprets/executes.
To do otherwise defeats the primary purpose of module load paths and makes build scripts more fragile.
Please do not do.
=> More informations about this toot | View the thread
Using a laptop without a battery is quite a curious experience so far. I really have to think carefully about changing context, because moving the laptop means shutting down gracefully, then booting later.
I wonder how long I'll need to do this.
I'm so happy that I have the slack it takes for this to be a curiosity or a mild annoyance, rather than a problem.
=> More informations about this toot | View the thread
This poor mid-2012 MacBook Air... it hasn't worked this hard in years. I can only imagine what it must feel like right now.
=> More informations about this toot | View the thread
I see #refactoring as an act of love. I see it as the opposite of "since I suffered (to make this code work), you must suffer (to understand this code)". Specifically, this relates to the "Clean Up Before Moving On" kind of refactoring.
=> More informations about this toot | View the thread
A discussion in our chat space at The jbrains Experience brought this 2009 article of mine back to the surface:
"Why I Try to Communicate in E-Prime"
https://blog.jbrains.ca/permalink/why-i-try-to-communicate-in-e-prime
=> More informations about this toot | View the thread
I toot again from toot, but also from kak. I don't know what value this has, but it feels nice.
=> More informations about this toot | View the thread
Hello, world. I toot from toot.
=> More informations about this toot | View the thread
=> This profile with reblog | Go to jbrains@mastodon.social account This content has been proxied by September (3851b).Proxy Information
text/gemini