Tag: development
-
How much does it cost to build an internal developer platform? – Tanzu Catsup
This week’s Tanzu Catsup is about how much you need to pay people to build your own internal developer platform: I think building your own platform is a terrible idea, especially for larger organizations. My co-host Tony ran the platform for Home Depot and now talks with other platform teams a lot, so I wanted…
-
Another go at LowCode
Another go at LowCode: It is a new era of app creation that is sometimes called micro apps, personal apps, or fleeting apps because they are intended to be used only by the creator (or the creator plus a select few other people) and only for as long as the creator wants to keep the…
-
SaaS businesses not looking good now: Traditional estimates for this scope of work: Method Estimate COCOMO (lines-based) ~20,000 hours Feature decomposition ~9,000-12,000 hours Industry benchmark 5-6 years solo, 12-15 months with 5 junior engineers Traditional cost $750,000 – $1,500,000 What I spent: $1,800. That’s a 99.8% cost reduction. It’s also not a fair comparison—traditional development…
-
“In software development, we have 18,000 developers at the company that use coding agents today to optimize our development process,” Hari Gopalkrishnan. “We’ve already seen 20% productivity [boosts] coming out of those parts of the lifecycle, which we are now reinvesting next year into new growth programs.” 🔗 Bank of America runs 270 AI models…
-
Guardrails in platforms
“Individual teams making rational decisions create organisational fragmentation.” // An overview of the impossibly fine line between restricting developers for long term agility and reliability, and giving them freedoms to perfectly solve their apps problems. 🔗 Golden Paths: One Size Does Not Fit All
-
ai-development-patterns, PaulDuvall – ”A comprehensive collection of patterns based on my experience for building software with AI assistance, organized by implementation maturity and development lifecycle phases. These patterns are subject to change as the field evolves.”
-
How Pair Programming Enhanced Development Speed, Focus, and Flow –
-
Identify, solve, verify – “My job is to identify problems that can be solved with code, then solve them, then verify that the solution works and has actually addressed the problem.”
-
Resume-driven Development
Good wastebook list this episode, but first… Even the Germans suffer from RDD Some people actually did a study on resume-driven development. I thought it might be a joke at first, but, no: it appears to be serious. I’m working on refreshing a paper on the pitfalls of building your own application platform (“DIY platforms”),1…
-
Azul CTO: Java at 30 Still Rules Enterprise Dev – Yes, and: Azul must have set a compare goal for this FY to get a, checks notes, “shit ton” of coverage.
-
Reports of Deno’s Demise Have Been Greatly Exaggerated – ”Most developers weren’t deploying simple stateless functions. They were building full-stack apps: apps that talk to a database, that almost always is located in a single region.” // People love the CRUD app. // Also, a tales from PaaS-land.
-
Augmented Coding: an Experience Report – Getting an app released requires so many things that humans will always find something to do, and more that can now be done better.
-
Some advice and good practices when integrating an LLM in your application – Yup!
-
Cycle Time – Time spent figuring out this nuance is time spent not coding and getting your apps out the door and kicking in the product management feedback cycle. Still, good discussion of the nuances of the phrase.
-
Kubernetes getting better at speeding up development – State of Kubernetes survey, 2024
Survey says… Kubernetes getting out of appdev improvement slump This is the chart I look forward to in our annual State of Kubernetes report1: It’s been a rocky few years as Kubernetes has gone mainstream. I pay attention to the “shortened software development cycles,” which you can see started going down. It’s been going up…
-
Developers are bad at estimating in at least three ways.
Midjourney: Olan Mills style photograph of software programmers standing around a conference table in 1980s sitcom style Software people are bad at estimating Here are three ways that software people (developers, mostly) are bad at estimating: Estimating the feasibility of writing code for new features, that is, the risk of failure – if the new…
-
Deploying the Swift Method to Modernize a Singapore Government Legacy System – Good description of what it feels like to be stuck in the legacy trap: “The [Singapore] government agency in this case study faced a similar issue with a legacy system that supported critical business processes, integrated with other business-critical applications, and was developed…
-
They were just wearing Levi’s because of what it symbolizes
Not much time for original content today: a Link Gourmand, my own links, the wastebook, and quick chair. Garbage Chairs of Amsterdam Garbage Chairs of Amsterdam, March, 2023 For several years, I took a lot of pictures of thrown out chairs in Amsterdam. Here’s a small selection of early ones – I’ll have to upload…
-
If it’s bullshit work, have the bullshit-artist do it – Using AI for Bureaucratic Toil Removal
Hey there! As I type this, SpringOne is being livestreamed right now! Chances are, you’ll read this when it’s over. But, you can go back and see today’s talks, and there’ll be more tomorrow and Thursday. If you’re interested in development, cloud native, and especially the question “what is VMware Tanzu?” today’s talks are for…
You must be logged in to post a comment.