We develop GitLab in the open, and we post regular video updates about our progress. This week I demo collaborative editing with y-rb.
https://t.co/yRjVLshNw2
#crdt#collaborative#editing
@ChristophGockel Right now we’re solving the context switch issue with fine grained sub tasks but until the last one is done the feature is not usable and we might realize that we have built the wrong thing for the last 2 weeks.
Has anybody some resources/exercises on how to slice user stories into smaller chunks. Breaking the story into small tasks (max 1 day of work) and deploy them behind feature flags is not the issue. My issue right now is that a single story sometimes takes 1-2 weeks.
@ChristophGockel It might not be desirable. For me it’s about working on a single thing at a time. If I don’t want to context switch I’m blocked for 2 weeks. With 1 day (or even smaller) stories I’m not blocked for that long and can react on urgent requests (eg bugs) without switching context.
I would like to remove the layer of technical tasks and replace them with value adding stories. By removing the technical tasks I believe the feature flag layer could be removed as well.
@wolframkriesing I would consider https://t.co/XKd2xge4OA as done. I have a feeling that devs prefer more active projects over stable ones. I personally don’t see much value in keeping myself busy fixing all the breaking changes in my unstable/cutting edge dependencies.
Good news everyone! Registration for SoCraTes 2022 in Soltau is now open! 🎉
👉 Apply for the lottery here: https://t.co/7tE0sze0FF
We are excited to meet you in person this year again! 😊
My experience with user stories is that when you pick one and then refine it down to something precise, you uncover many many more stories in the process—way more work than you can do in a few weeks. 1/3
@codecopkofler @Sclable In the upcoming months I’ll help to slice a monolithic application into microservices in Kotlin. I think that tools like eventstorming can give a good insight about coupling between different functionality and can help to define service boundaries.
Today was my last day @Sclable and I couldn't be more happy for the last years with these incredibly talented people. For the future I'll start my journey as a freelance software developer and hope to help teams wherever I can. I'm really excited for the upcoming challenges.
@codecopkofler @Sclable I personally want to help teams to reduce their cycle times by opening up the conversation to non technical people using EventStorming. As a result I want to help the dev team to implement these results using XP and DDD. I don’t want to focus to much on tech stack right now.
Writing tests for the new Node.js test runner:
import test from 'node:test';
import * as assert from 'assert/strict';
test('synchronous test', (t) => {
assert.equal(1, 1);
});
test('asynchronous test', async (t) => {
assert.equal(1, 1);
});
https://t.co/ZUoEYkIzuG
A problem that is endemic to the whole developer community is the urge to "rewrite everything". It is the one of the most harmful practices in software engineering.
Why? (thread)
@decksetapp my slides are not updating automatically whenever I save my .md file. This makes the app almost unusable for me as I have to close and reopen the presentation for each little change. Is there a workaround?