Meta woke up this morning and unleashed some new automoderation tool which has nuked hundreds, possibly thousands, of massive groups.

The community is immediately blaming AI, and are rightly furious at Meta.

www.reddit.com/r/facebook/

I'll be talking to Coder today (9:00 PDT, 12:00 EDT, 18:00 CEST) about my research on the standardisation of development environments and its benefits and challenges, as well as the possible security and productivity costs of bad standardisation operationalisation

The industry is unprepared for this because in the effort to please clients in the now, we are poisoning our trust going forward. For those working as market researchers and analysts, it is crucial to push back against those who seek rapid turnaround to client demands at the expense of good work.

There is a distinct lack of statistical rigour, data literacy, and analytical effort by a large proportion of the market research industry.

As more MR organisations push towards AI to solve all their problems we are going to see a vast decaying of research quality, and a loss of trust.

It may be old, but this is bad market research advice. Like everything, it is about the implementation rather than the existence of the option itself.

What it speaks to more crucially, is that the market research industry struggles to analyse results that can't be shown in a pie graph

Pie charts are always bad data communication, and there is never a need to use them.

This will not prevent everyone asking for every visualisation to be a pie chart.

This is our burden to bear

I need to write up a piece about the power of 'i don't know/unsure' in survey design and analysis because it is exhausting watching people slide over the insights from it

Thank you 😊

The #CNCF ecosystem gaps report (based on our data at SlashData) is a good example of how to educate, inform, and support developers on this particular move and migration. Discover where developers think there are gaps, and offer the current best solutions, to help discover the new challenges.

When we survey developers on these topics, we always make sure to get an understanding of who the developers are and what their stacks look like, to try and make it easier to understand the relationship between complexity and experience/competency, and thus how to target solutions.

Many devs trying to implement these are often poorly supported, trained, and equipped to handle all of the issues they are dealing with. And starting off on patched together solutions means the call is coming from inside the house, and the complexity can't be solved by applying a new layer on top.

Managing complexity is a major issue in modern development, but those developing many tools to handle this, especially in the cloud native space, are very talented devs with a huge amount of exposure to all of the processes that lead to this moment.

An important consideration when looking at reports of #developers and administrators describing new technologies or processes as complex, is to disentangle is the technology complex in and of itself, or are there groups of developers just with less experience to these technologies in general?

During the research for the return of the #CNCF Tech Radars, we asked developers about where they *feel* there are gaps in the cloud-native ecosystem. This supported the new CNCF Ecosystem Gaps report, which both summarised the findings and recommended solutions to explore

As @onlydole.dev mentioned during his #Kubecon keynote, the #CNCF tech radar is back, and we are enjoying the discussion and feedback that's been shared. Working on this research was really cool, and I am excited to see it out in the world www.youtube.com/watch?v=TnYu... www.cncf.io/reports/cncf...

Hi Liz, do you remember which presentation/panel this was? I am the researcher who worked on this report for CNCF and I am curious to see its use in the wild. Thanks

Our research making impacts at #CNCF #Kubecon

My particular areas of focus are on #cloud developers, #DevOps practices, IoT (particularly at the edge), and developing new ways to assess software supply chain security at organisations

Hello all!

I'm an analyst and consultant who studies the 'developer economy', i.e. the behaviours and practices of software developers. I'll be using this page to share interesting snippets from my work, as well as public reports and interviews.

#softwaredevelopment #developers