Here's a video on YouTube making the case for why agile was an innovative methodology when it was first introduced 20 years ago.
However, he argues these days, daily scrums are a waste of time, and many organisations would be better off automating their reporting processes, giving teams more autonomy, and letting people get on with their work:
First, it's worth noting that many organisations that claim to be "agile" aren't, and many that claim to use agile processes don't.
Just as a refresher, here's the key values and principles from the agile manifesto: http://agilemanifesto.org/
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Business people and developers must work together daily throughout the project.
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
Continuous attention to technical excellence and good design enhances agility.
Simplicity--the art of maximizing the amount of work not done--is essential.
The best architectures, requirements, and designs emerge from self-organizing teams.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Your workplace isn't agile if your team is micromanaged from above; if you have a kanban board filled with planning, documentation, and reporting tasks; if your organisation is driven by processes and procedures; if you don't have autonomous cross-functional teams.
Yet in many "agile" organisations, I've noticed that the basic principles of agile are ignored, and what you have is micromanagement through scrums and kanban boards.
And especially outside software development teams, agile tends to just be a hollow buzzword. (I once met a manager at a conference who talked up how agile his business was, and didn't believe me when I said agile was originally a software development methodology — one he revealed he wasn't following the principles of.)
Dites, développeuses z'et développeurs, régulièrement, dans mon cercle professionnel direct, j'entends dire que vous n'aimez pas #CSS (voire #HTML).
Question sérieuse et qui n'appelle pas à réveiller quelconque troll ou débat sans fin : pourquoi n'aimez-vous pas ce langage ?
Qu'est-ce qui vous chiffonne, vous rebute ?
D'où vient votre éventuel manque d'intérêt ?
J'ai déjà des éléments de réponse proches de moi, mais je suis curieux d'élargir la question ici.
What do you like to read for work or in your spare time? (That's related to your job or code more generally). Trying to get a list of content that's actually good and read by real people vs propped up by algorithms.
Send links if possible or give names of sites / blogs / creators.
🧵1/2. Here’s something non-coders probably don’t know about development. Code is written in English. That’s a privilege that English speakers have in this space.
There are custom words used in code. They can be written in other languages. But reserved words that are part of the core language must be in English.
For example in HTML we begin the content area of the structure using <body>. A Spanish-speaking coder can’t use <cuerpo> for that.
So did I mention that no company or government pays me for the work I do?
But you can support my work if you want to live in a world where we have the Small Web as an alternative to the Big Web of Google, Facebook, and other people farmers.
Very excited about the latest feature/workflow I’m adding to Kitten. I call it… 🥁
✨ Streaming HTML ✨
Implement back-end functionality and stream HTML updates to the client without writing any front-end JavaScript.
Just give your forms names and listen for them in an onConnect() handler you export from your page. Kitten handles everything else – setting up a WebSocket route for you, mapping triggers to events, etc. – thanks to Kitten + #htmx magic 🪄
Just updated a server I hadn’t touched in over six years from Ubuntu 16.04 → 18.04 → 20.04 → 22.04 and it all went smoothly; not a single issue.
I can’t wait for a server with Fedora Silverblue-style upgrades (CoreOS?) that’s supported by the major VPS providers in default images. Tried a while back to get Hetzner to support CoreOS but the process appears somewhat stuck:
I'm as excited about the rumors of improved desktop modes and video out support for the Pixel 8 as the next guy, but we've fielded these kinds of rumors before.
Currently the only phone I have that can run an Android 14 beta, AND has video out, just did this using the desktop mode in Android dev settings.
Which is even more broken than the A13 desktop mode, which was already almost nonfunctional from the A12 mode.
I really WANT Google to give us a Pixel 8 with a proper desktop or tablet large screen mode, but I'm not getting my hopes up until we see the phone in action.
¹ Previously, I was doing 404 to 302 but 302 redirects do not keep the request method so 307 is the correct redirect to use. I’d been meaning to update the site for ages and so I finally made some time to do so this week.
OK... here is a question (#PHP but other #dev communities are welcome to comment.
When building a decoupled app, do you consider the usage of something like ClassWithAnnoyingName::class
(not to call the class, but to reference the name as a string and to simply avoid to type it out) as coupling?
IMHO, it is not
it is very trivial to replace with its string value if needed
I’ve been looking for an ngrok alternative for a while now that’s (a) affordable (b) easy to use and (c) works with Kitten¹. Today, after testing a bunch of them again and getting fed up, I found LocalXpose that checks all the boxes.
I signed Small Technology Foundation up as an affiliate so if you use this link to check it out, we’ll get 40% of your $6/mo pro account fee should you subscribe:
First time poking around with Dev Drives, so doing a little performance testing by measuring dotnet build after git clean -xdf for @xunit (main branch).
On NVMe (NTFS): 17.5s
On SATA (NTFS): 17.9s
On VHDX (ReFS): 14.4s
On VHDX (ext4): 11.7s
The top 3 are built in Windows, and the bottom 1 is built in WSL 2 (Ubuntu 22.04). I wanted to be able to compare the two VHDX options.
Looks like Dev Drive is a win, but not as big as moving to Linux & ext4.
A fifteen-second demo of how you can create a toast message in 42 lines of code¹ without writing any client-side JavaScript using Streaming HTML² in Kitten³.
Still looking for usable #UML software
It needs to be visual (no code) and able to handle rather big modules and submodules
Sometimes have the feeling I am the only #dev that still uses #uml
We’re known for 3 things: Freeware, software, and client design work. Lately, we’ve spread the word about the first 2. Now, to better focus on the third, we’ve redesigned our site.
For over 25 years, the Iconfactory has made software beautiful. We craft icons, apps, & user experiences for clients large & small. Our new site highlights all we offer, and we’d love to help you with your project.
HELP!
Our Matrix server and/or Element client just doesn't seem to invite people to rooms, properly. Is there anyone out there with a LOT of matrix experience who can help us figure this out? It's been a problem for months, and delays a really interesting project;