You don't need a full-featured testing framework, or something that outputs in JUnit format, to get the value of a red-green-refactor loop.
All you need is a feedback mechanism, which can be as simple as "does the exit code for this process indicate an error or success?".
Kent Beck's test-commit-revert demo using python does exactly this - no importing a framework or test runner, but leaning on python's built-in `assert` keyword.
https://youtu.be/Aof0F9DvTFg?t=220&si=D7afjzT2GvTEhTQn
What's your personal minimal acceptable lead time for a conference talk?
If you submit a talk proposal, and it's accepted, then you'd expect to be notified of that acceptance some time prior to your talk, so you can prepare and rehearse well and sort work and travel around the conference. What's that minimum time for you?
(Boosts would be nice, thanks!)
[ ] 2 weeks
[ ] 4 weeks
[ ] 6 weeks
[ ] 8 weeks or longer
This thing with #Fosstodon has to be the whitest thing I've seen on here in months, lol. Like DeepL and LibreTranslate (if you don't want to use Google) are right there. There's laziness and then there's this. That and considering mutual aid posts to be spammy?
Say less. Definitely going to look into purging his links from the IndieWeb wiki or at least add a warning of Angolcentricism.
Attached: 1 image
our induction stove is here. I got the guy who installed it to touch a burner right after it heated a pan, and he was like WOAH.
magnets, man. 🤯
Interviewer: So now do you have any questions for us?
Candidate: Yes, thank you. I was looking at your LinkedIn profile and didn't see any evidence of side teams that you manage, are you actually that passionate about being my manager? I'm going to give you a scenario where a team got into conflict, could you please show me on the whiteboard how to reverse it in linear time?
I was one of the first ten full-time employees at Stoplight and launched some of the open source work that was called out in the acquisition. it's been cool to see it grow from the start, contribute to a whole OpenAPI ecosystem, and continue to live on in the future.
https://blog.stoplight.io/stoplight-joins-smartbear-a-cto-perspective
We have a wonderful Slack channel called #why which is filled with questions like "why do we do <thing>" or "does anyone remember why we do <thing>"
1. It's kinda helpful when you scale up staff a lot in approximately one year
2. Even the CEO asks why questions!
3. At year 6 or so of a startup there are lots of decisions to be reconsidered
A green test suite is a blank canvas, and a blank canvas is a paralyzing place to start.
A failing test is a pointer to the next step. When I end the day with a failing test, I know exactly where to begin when I get back. The perfect kickstart to get into flow.
Was thinking of making a horror movie. For one day every year all repos are public and there’s no checks on pull requests. No tests are allowed and CI/CD won’t block you.
The Merge.