rotbart

This is a similar workflow to speckit, kiro, gsd, etc.

I levelled up my Claude Code workflow by giving it the ability to see its own front-end output — automatic screenshots captured during system/e2e tests, wired into a custom Code command that visually inspects every captured frame.

Two files, a few lines of config, and a meaningfully better feedback loop.

I can't download it, as it appears to be US only. Based on the screenshots, without 'feels like' support throughout the forecast (not just for current conditions) it wouldn't be useful where I live.

Hurrah, its dumb answer to the now classic "the car wash is 100m away, should I drive or walk?" appeared very quickly.

This is not exclusive to the East, but any culture with a high cost of expression. Recent interview with a Russian CEO, talking about how they have "growth across the board, only in the negative direction"

Nothing wrong with the attributes the author groups under 'transparent leadership', but the article shows a certain misunderstanding of servant leadership.

At the core of servant leadership is the idea that leaders shouldn't hoard power, but instead share it and empower their reports. That they are accountable to their reports, rather than the other way.

Nothing to do with acting like a parents and becoming a single point of failure.

So... clickbait title for an article that could have been called "Delete flakey tests"...but then and most of us would have just gone "yep" and not clicked.

Great talk about this... https://www.youtube.com/watch?v=j2AQ9eTZ3-0

Hyrum's Law especially applies when you have consumers of your APIs that violate Postel's Law. To minimise those in the past, we've introduced intentional jitter in our API responses that while didn't violate the schema prevented unintentional reliance on behaviour that wasn't intentional[1].

[1]: <https://medium.com/pageup-tech/update-on-driving-client-resi...>

Add: '-site:pinterest.com' to your Google image search to avoid pinterest results.

As a former 13year old, that would be the end of 13 year olds using iMessages... I smell an opportunity.

That's where red-green TDD and pairing comes in. Unit tests != class level tests.

Overall would recommend leveraging the schema from JSONResume (https://jsonresume.org/schema/) that supports all of the above

More information: Wei Li et al, High potency of a bivalent human VH domain in SARS-CoV-2 animal models, Cell (2020). DOI: 10.1016/j.cell.2020.09.007 http://dx.doi.org/10.1016/j.cell.2020.09.007

It's a very simplistic tool, but it is great to help visualise and illustrate some systems. It helped me demonstrate the dynamic between technical complexity, delivery pressure and velocity (then add refactoring) https://medium.com/pageup-tech/the-system-of-technical-compl...

This just prompted me to cancel my Zoom subscription... I could live with all the security flaws (which were patched quite rapidly) but not with this kind of unethical behaviour.

Reminds me of how we subverted Postel's Law to uphold Postel's Law https://medium.com/pageup-tech/update-on-driving-client-resi...

Shameless request from me as well. Thanks!

Our technology gives a much better identification of noun senses (http://springsense.com/api/)

Favourite would be NuditySearch?