Showing posts with label developer. Show all posts
Showing posts with label developer. Show all posts

Pipi Data Centre Operational

Mike's Notes

Very good news for Pipi.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

26/02/2026

Pipi Data Centre Operational

By: Mike Peters
On a Sandy Beach: 25/02/2026

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

The long-planned migration of Pipi 9 to its own data centre has been completed. It took 2 weeks to execute. The existing setup was split into an office network connected to the internet and an isolated data centre that is not connected to the internet.

Starting from zero

The initial data centre consists of a single 45U rack and some other shelving, with mainly older equipment. It will do for a start and can grow as more racks are added, equipment upgraded, and more servers are added, etc.

External hard drives being used in the shift

Issues

  • Terabytes of data on backup hard drives to shift
  • Clean reinstalls of many operating systems
  • 14 machines to configure
  • Adobe CS4 does not like Windows 11
  • Making do with what is available now
  • Go slow, think twice and get there faster

Opportunities

  • Pipi on 24x7x365
  • All systems can be turned on using multiple servers
  • DevOps automation is now possible
  • The development cycle will speed up 10x
  • The road to Pipi 10 with BoxLang is now open

Whats next

  • Seat-of-the-pants experimenting to tune the setup
  • Stress test to build resiliency and reliability

Developer access to Pipi, is coming

Mike's Notes

The data is precise on this one. Unfortunately, the current developer interest in NZ and Australia is 3% and 0%, respectively. I also can't find anyone in NZ who has the slightest technical understanding of what I'm doing. But there are plenty overseas, especially in MLOps. We speak the same language, even if the architecture and algorithms are radically different. Also, top-grade mathematicians get it. Internally, Pipi 9 uses a lot of maths.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

08/12/2025

Developer access to Pipi is coming

By: Mike Peters
On a Sandy Beach: 02/12/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

The problem

To launch Pipi 9 with limited resources in 2026, the effort needs to be highly focused on developers who build large enterprise systems and have experienced failure, cost overruns, and staggering complexity. This is for them.

Waste

The staggering annual global cost of IT failures on big projects is around $US 3 trillion. How many schools or knee replacements would that be?

  • 15% succeed
  • 25% makes no difference
  • 60% fail

Web traffic stats

The steadily growing web traffic statistics of public interest in Pipi 9 are becoming very clear.

Since early 2019, the total traffic stats by country are;

  • China 19%
  • Singapore 16%
  • United States 15%
  • Hong Kong 11%
  • Brazil 10%
  • TOTAL 71%

Developer Accounts

The initial paid Developer Accounts will be restricted to experienced DevOps teams with great internal culture in those five countries. That also affects the language, currency, hours of support availability, etc. Later, as interest and resources grow, that list of countries can be expanded.

Personal Accounts

The free Personal Accounts will initially use an English interface and will not be restricted by country of residence. They will get community support.

Enterprise Accounts

The initial paid Enterprise Accounts will be supported by their associated Developer Accounts, who can charge them whatever they want for that service. They will initially use an English interface and will not be restricted by country of residence. Developer Accounts will be able to translate UI and documentation into any language and writing system.

Pipi 9 is in hiding

This engineering blog and the many other Ajabbi documentation websites are deliberately hidden from search engines. People are visiting because they are curious, as I write notes to myself and build, learning as I go. It is not easy to find the technical documentation unless you are really interested, clever and very determined. That has helped me find some early, keen technical fans who provide testing and feedback. It has also protected me from being overwhelmed by enquiries.

Communication constraints

I am a very slow writer, using assistive technology, have hearing problems and prefer video chats with people who speak good, clear English. I don't speak any other language apart from tiny bits of Maori, French and Spanish.

SEO and GEO

The SEO/GEO settings will be fixed when

  • Pipi 9 matures and becomes ready for public use
  • Community support is in place
  • Bugs fixed
  • Enough self-help documentation to help people get started.

Developer Account waitlist

There will be a signup queue to control demand, so scaling is steady with a positive resource feedback loop to solve the chicken-and-egg problem. The small queue is growing now. I will pick the best candidates with the highest chance of success. They will gain a first-mover advantage in building large, custom enterprise systems faster and at a much lower cost. The first ones will get free unlimited support. 

Relying on word-of-mouth recommendations.

There will be no marketing or sales, just good, clear documentation, live demos, and regular bookable office hours (NZ daytime) for having a chat.

Inflexion point

In the future, as workspaces mature and Pipi 10 becomes even easier to work with, resource constraints will disappear, teams will grow, and an inflexion point will be reached. Anyone will then be able to sign up.

Agents in Production on replay

Mike's Notes

The videos of the talks given at the recent Agents in Production are now available to watch. The talks are technically excellent. I watched some of it (It started at 3 am NZ Time), so I will watch the rest from now.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library > Subscriptions > MLOps Community
  • Home > Handbook > 

Last Updated

24/11/2025

Agents in Production on replay

By: 
MLOps Community: 24/11/2025

The Virtual AI Event That’s Actually... Fun

We know what you’re thinking: another virtual conference. Talking heads, awkward silences, and the constant urge to check your email… we’ve all been there.

Not this one.

100% AI Agents in Prod. BUT This Isn't Just Another Zoom Link.

Welcome to Agents in Production: the latest edition of the MLOps × Prosus AI Virtual Conference.

We’re bringing together the brightest minds building AI agents, with a high-energy format designed to keep you hooked from start to finish.

Last year, companies stopped experimenting with agents and started deploying them in the real world. We heard from the pioneers who turned hype into working systems - and this year, we’re doubling down.

Expect real progress, real lessons, and real breakthroughs shaping the future of agentic AI. You’ll get cutting-edge, actionable insights that move you from experimentation to full-scale deployment.

30+ Talks on AI Agents. I Promise You Won’t Log Off Early

Why Attend:

  • Talks from top experts – Real-world lessons, practical insights, and breakthroughs defining agentic AI.
  • Hilarious skits & live music – Because learning should be fun.
  • High-energy engagement – Interactive moments that make you part of the action.

If You Miss This, You’ll Miss:

  • Hard-won lessons – How leading companies are successfully deploying agents at scale.
  • Deep dives – Technical sessions and workshops from the voices shaping the next generation of AI.
  • Global connections – Network with innovators and practitioners across the ML community.
  • This is your chance to get up to speed on the global AI scene, connect with innovators, and experience a virtual event you’ll actually enjoy.

See you there! 

Speakers

  • Chip Huyen, Researcher @ Tep Studio
  • Aditya Gautam, Machine Learning Technical Lead @ Meta
  • Teodora Musatoiu, Solutions Architect @ OpenAI
  • Adel El Hallak, Senior Director Of Product @ NVIDIA
  • Panos Stravopodis, Co-Founder & CTO @ Elyos
  • Jiquan Ngiam, CEO and Co-Founder @ MintMCP
  • Chenyu Zhang, Founder @ GlowingStar Inc.
  • Rekha Singhal, Head Research @ Tata Consultancy Services
  • Santoshkalyan Rayadhurgam, Engineering Leader @ Meta
  • Swati Bhatia, Product Manager @ Google
  • Arushi Jain, Senior Applied Scientist @ Microsoft
  • Donné Stevenson, Machine Learning Engineer @ Prosus Group
  • Mefta Sadat, Staff Software Engineer @ Loblaw Digital
  • Sam Partee, Co-Founder @ Arcade.dev
  • Sachi Shah, Product Manager @ Sierra
  • Jasleen Singh, Staff Solutions Architect, Generative AI @ Google
  • Sanjana Sharma, AI Strategist @ Distyl AI
  • Artem Yushkovskiy, Sr ML Engineer @ Delivery Hero SE
  • Rosemary Nwosu-Ihueze, Founder @ Soteria
  • Euro Beinat, Global Head AI and Data Science @ Prosus Group
  • Washington Amolo, Product Developer @ NaviSmart AI
  • Benjamin Guo, Co Founder @ Zo Computer
  • Hamed Taheri, CEO & Founder @ Personize.ai
  • Phil Stafford, Principal Consultant, Cybersecurity & AI @ Singularity Systems
  • Quinten Rosseel, AI Engineer @ Wobby
  • Dirk Petzoldt, Co-Founder @ Explai.com
  • Tom Kaltofen, Engineer @ mloda
  • Rachitt Shah, Applied AI consultant @ Transfrm Labs
  • Vitor Balocco, Co-founder @ Runlayer
  • Frank Wittkampf, VP Applied AI @ Databook
  • Laurel Orr, AI Staff Software Engineer @ Stacklok
  • Benjamin Hindman, Founder & CEO @ Reboot
  • Ben Epstein, Co-Founder & CTO @ GrottoAI
  • Matt Sharp, AI Strategist and Principle Engineer @ Flexion
  • Audi Liu, Senior Product Manager @ Inworld AI
  • Olga Pavlov, Head of Product @ OLX Group
  • Isabella Piratininga, Director of Technology & Innovation @ iFood
  • Paul van der Boor, Senior Director Data Science @ Prosus Group
  • Demetrios Brinkmann, Chief Happiness Engineer @ MLOps Community
  • Ricky Doar, VP of Solutions @ Cursor
  • Nishikant Dhanuka, Senior Director of AI @ Prosus Group
  • Chiara Caratelli, Data Scientist @ Prosus Group
  • Simba Khadder, Sr. Manager & Software Engineer @ Redis

On a Sandy Beach, database version 2 is underway

Mike's Notes

In May, after manually reformatting every page and post of "On a Sandy Beach," I wrote.

"A blogging module needs to be built and added to Pipi 9 CMS. This could then be used to create blog posts using an underlying database, which could be modified to be more useful."

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

28/09/2025

On a Sandy Beach, database version 2 is underway

By: Mike Peters
On a Sandy Beach: 28/09/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

The datamodel version 2 to support blogging is now being built. It is designed to support On a Sandy Beach. Yesterday, this Blogger post index was scraped and imported to initially populate the database.

In future, the blogging module will also support other blogs/newsletters, including the Ajabbi Research Monthly Newsletter, which begins next month in October on Substack.

The new database and blogger will be synced while other jobs are completed, including;

  • The tags need consolidating
  • The same tags will form a topic map and be used across Ajabbi
  • etc

Data Model version 1 (current)

  • Mike's Note
  • Resources
  • References
  • Repository links
  • Date Updated
  • Title
  • Page Url
  • Author
  • Source publication
  • Date Created
  • Author description
  • Body of the article
  • Tags
  • Comments

Data Model version 2 (now being built)

  • Title
  • Page Url
  • Site-wide Navigation
  • Site-wide Breadcrumb
  • Mike's Note
  • Author
  • Source publication
  • Date Created
  • Author description
  • Body of the article
  • References
  • Further Reading (replacing References)
  • Articles
  • See Also (cross-links to Ajabbi.com website pages, replacing Repository URL)
  • External Links (replacing Resources)
  • Keywords (replacing Tags)
  • Sharing
  • Updated
  • Forum (replacing Comments)

The 2025 DORA survey is open now

Mike's Notes

Note

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library > Subscriptions > IT Revolution
  • Home > Handbook > 

Last Updated

03/07/2025

The 2025 DORA survey is open now

By: 
DORA: Copied 03/07/2025

The DORA research program is dedicated to helping technology teams get better at getting better. That journey often starts with a moment of reflection.

We invite you to take 10 minutes for that reflection with the 2025 DORA Survey. Participants often tell us the survey itself is a valuable self-assessment, sparking immediate ideas for how their team can improve.

Your anonymous contribution will also power the industry’s most trusted research on software delivery performance. This year, we’re exploring crucial topics like AI integration, platform engineering, and developer well-being.

By participating, you:

  • Discover potential improvements for your team just by taking the survey.
  • Shape the industry’s understanding of what defines elite performance in 2025.
  • Help create the benchmark you and your peers will use to drive change.

This research is strongest when it includes diverse perspectives. Whether you’re a Software Engineer, Data Scientist, Product Manager, QA Developer, or anyone else who participates in the creation and delivery of software your voice is critical.

Thank you for helping us all get better at getting better.

Consider holding a team discussion about the survey using our discussion guide.

Growing the development forest - with Martin Fowler

Mike's Notes

This interview with Martin Fowler was in a recent Refactoring Newsletter.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library > Subscriptions > Refactoring
  • Home > Handbook > 

Last Updated

17/05/2025

Growing the development forest - with Martin Fowler

By: Luca Rossi
Refactoring: 24/01/2024

Martin is chief scientist at ThoughtWorks. He is one of the original signatories of the Agile Manifesto and author of several legendary books, among which there is Refactoring, which shares the name with this podcast and this newsletter. 

With Martin, we talked about the impact of AI on software development, from the development process to how human learning and understanding changes up to the future of software engineering jobs.

Then we explored the technical debt metaphor, why it has been so successful, and Martin's own advice on dealing with it. And finally, we talked about the state of Agile, the resistance that still exists today towards many Agile practices and how to measure engineering effectiveness.

(03:29) Introduction
(05:20) Development cycle with AI
(08:36) Less control and reduced learning
(13:11) Splitting task between Human and AI
(14:48) The skills shift
(20:17) Betting on new technologies
(27:22) Martin's Refactoring and technical debt
(29:24) Accumulating "cruft"
(33:14) Dealing with "cruft"
(37:24) The financial value of refactoring
(42:04) Measuring performances
(46:19) Why the "forest" didn't spread
(56:11) Make the forest appealing

Show notes / useful links:

MDN as an example website

Mike's Notes

MDN is a Mozilla website for developers.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

18/05/2025

MDN as an example website

By: Mike Peters
On a Sandy Beach: 29/08/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

MDN website structure.

  • References
    • HTML
    • CSS
    • JavaScript
    • HTTP
    • Web API's
    • Web Extensions
    • Web Technology
  • Guides
    • MDN Learning Area
    • HTML
    • CSS
    • JavaScript
    • Accessibility
  • Plus
    • Overview
    • AI Help
    • Updates
    • Documentation
    • Help
  • Curriculum
  • Blog
  • Tools
    • Playground
    • HTTP Observatory
    • AI Help

IBM Developer as an example website

Mike's Notes

IBM Developer has an interesting way of organising content on the developer home page.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

18/05/2025

IBM Developer as an example website

By: Mike Peters
On a Sandy Beach: 28/08/2024

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

IBM Developer website structure.

  • Build
  • Learn
    • Guided projects
    • Tutorials
    • Articles
  • Explore
  • Code
  • Engage

ajabbi on reddit

Mike's Notes

A subreddit has been created for Ajabbi and Pipi to foster Developer Relations (DevRel).

According to the 2024 Stack Overflow Developer Survey, Most developers visit websites daily for technical information and post questions and answers. One of those websites is Reddit, so Ajabbi needs to be there with Pipi.

Anyone can read the Ajabbi community on Reddit, but only registered people can post. This is to keep spammers out.

At the same time, the Pipi CMS static page generator is slowly publishing, testing, and organising the pages of Pipi's technical documentation on a public website.

A regular engineering newsletter is being organised.

This is part of many steps in sharing pipi with developers.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

18/05/2025

ajabbi on reddit

By: Mike Peters
On a Sandy Beach: 21/08/2024

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

words

The State of ...

Mike's Notes

Each year, Sacha Greif publishes regular surveys on using various web technologies. These surveys involve the opinions of tens of thousands of web developers and show trends over time. The reports are published in many languages and are considered authoritative.

Resources

  • Resource

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

17/05/2025

The State of...

By: Sacha Greif
sachagreif.com: 2024

Reports

Resources

"This whole thing started because of my own confusion. Way back in 2016 I knew I needed to step my web development game up, but I didn’t know where to start or which framework to pick. I figured other people might be struggling with the same issue, and so the State of JavaScript survey was born.

Later on, thanks to Raphaël Benitte’s dataviz expertise we were able to not only turn the State of JavaScript survey into one of the biggest developer surveys around, but even launch the State of CSS survey, which itself has gone on to play a key role in the ecosystem by informing browser vendors’ roadmaps.

Then Alexey Pyltsyn helped us manage volunteers to translate the surveys in over 25 languages, Sarah Fossheim gave us a hand with accessibility, Chris Kirk-Nielsen contributed some amazing t-shirt and logo designs, Kilian Valkhof pitched in to help with mobile testing, and Philip Jägenstedt helped unlock vital funding for the surveys as well as connect us with key players in the ecosystem.

And today, thanks to Eric Burel’s back-end know-how we’re building a new survey platform and using it to launch a third survey, the State of GraphQL.

Take all these people; add many more contributors, volunteers, and translators; and finally me, Sacha Greif; and what you get is an amazing community of developers spanning the globe. We needed a name for this collective, so say hello to Devographics " - Sacha Grief

Google Cloud Next '19

Mike's Notes

My notes on discovering more about GCP.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

11/05/2025

Google Cloud Next '19

By: Mike Peters
On a Sandy Beach: 09/04/2019

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Google is holding a 3-day developer conference Cloud Next '19 in San Fransisco April 9-11. It started today at 4am NZ time.

6 streams are running at the same time, covering a variety of topics.

All of the conference sessions are available live-streamed and also on-demand. I'm watching all the conference sessions.

Here is a playlist of all sessions.


I'm following.

  • Running on cloud, on-premise and multi-cloud.
  • Data storage.
  • Avoiding vendor lock-in.
  • AI strengths and weaknesses.
  • Security.
  • Product demos.
  • Google Cloud road map.

The conference and many previous conferences are also available on YouTube.

There were 32 recorded sessions from the first day alone, so 90 hours of watching are coming up.