开云体育

Many devs are still doing test-after. I paired with a guy on my team who is doing so - and he was having the whole idea difficult to understand: after all, isn’t a test something you do to see how

I'm here. Speaking in generalities, Swift devs as a whole are still getting used to test-after (and not even doing that for SwiftUI). Very few Swift folks are doing TDD. ________ Jon Reid, Trainer and

a) yes I had ChatGPT resolve some nasty CSS interaction issues. It was conversationally incremental and reasonably effective. b) no I have not tried to get it to help with TDD. I wonder about the

Of course, the snippet used here is (intentionally) quite simple, and probably nothing like a real-world scenario. Generating insights from an LLM above and beyond small “toy” scenarios (more like

Here in the middle of 2023 we see an AI bubble in the stock market - launched by OpenAI's release of ChatGPT. ?One can not turn on an info feed without hearing about AI these days. ?It is hotter

Good points. I wanted to add that lists are often maintained as "awesome <something>" on github. For example, "awesome python": https://github.com/vinta/awesome-python A search for "awesome unit

Maybe it is my bad mood ... but lots of things are dying (just saw Google Domains sold to SqSpace are they still alive?) - and we humans are better at denial than acceptance as a WAY, as part of LIFE.

Whatever happens, I think communication continuity is the key. We should try to make sure people don't get left behind. In this thread, I've heard about a subreddit, a youtube channel, a substack, and

Here's a link to a recent video on refactoring that I found interesting. Maybe a good topic for discussion: Gilding the Rose: Refactoring-Driven Development - Kevlin Henney - ACCU 2023 | | | | | | | |

I think this group is significant in learning TDD and refactoring, and I'm following up and picking things up whenever I have time. As far as I can tell,? what is being said is not as important as

I really dislike how in discord you need to be invited, however, it seems to be where many are headed. brought to you by the letters A, V, and I and the number 47

Hi, folks. When we had the idea to rescue this group several years ago, I wondered what would happen, even though I had no concrete plan for it. The most I've done so far is lightly promote this group

In the previous post, by "understand", I mean are specialists in both the topic and how to research that topic.

I would not advocate engineering faculty attempting to apply sophisticated social science research techniques, partly because it takes years of work to learn how to do it right and partly because it

Perhaps some pointers to examples of research you approve of would have helped here? I would have thought that when talking about developer experience, "feeling better" is potentially a valid data

I fully agree with Steve's comments, and I'd like to add that even if you did pursue the avenue of developing the same system using the non-Agile methods, and without TDD, and then developing the same

I read it. The theoretical portion was not new to me, having done TDD and Agile, taught it in University and customer sites, and wrestled with how to actually prove it is better for several years. The

I am all open to criticism to improve the work BUT you need to read the paper first. The survey is just one evidence I've used, there is a strong theoretical component in the paper. The survey is

I'll add what I always say about such papers: We all agree with the motivations - it is preaching to the choir. The surveys mean nothing because of the bias in the sample being surveyed. To me, such

TL;DR: TDD is good not only in terms of how it helps the design, but it also favor our mental conditions to be more productive.