okovooo

For many years, I used a different approach to memo() than React. I liked it, but I didn't implement it in the most elegant way. I tried many different options, but the results weren't satisfactory. Besides memo(), I was annoyed by the inability to move elements between parents. But what I really like is working with mutable data and the ability to use any source.

I was planning a new attempt at implementing a React extension, but I came across a discussion about AI defaulting to React. And the thought crossed my mind, "Why not write an entire framework?" Given the AI-First trend, why not write libraries in this style? Perhaps the library will be useful for more than just me. Furthermore, the specification and tests can be used to test the capabilities of different models, which is something I'd also like to try out eventually.

What makes you think I'm a bot? At least look at my GitHub history.

Did you pass the captcha yourself?

I thought it would be funny to repeat my previous post. And I also wanted to respond to the comment that said they could repeat ooko in 6 days.

The decision to write the library from scratch, rather than building an extension over ReactJS, was purely spontaneous. I didn't think a topic for a post here would come up so soon. This library is kind of a showcase of what's possible with free chats, a subtle jab at React developers, and a benchmark to see which AI writes code better. Oh, and it also features some solid ideas that I’ve been using for a decade already.

Performance isn't the only metric that matters; developer experience and architectural flexibility do too

This is a minified code.

Your comment was the first, but it's the hardest to answer.

I started doing this project when a new manager joined the team. And his first decision was to change the processes by rebuilding the kanban board. The team as a whole was initially satisfied with the board, which had been built for a long time with the previous two managers. Everyone began to propose their requirements for the kanban board, but the new manager did not hesitate to do as he saw fit. And in the future, this story was repeated with new managers.

If you take into account all the wishes, then the board becomes very large, both in width and in height. That's why I don't criticize new managers. In many ways, this is a consequence of the tracker's functionality.

Different types of work have different stages. For example, a developer needs a "code review" column, someone needs an additional "approval" column, etc. My idea was to give each type of work its own board. And on the task card, display which subtasks are currently being worked on. As a result, we would have unloaded the main kanban board, and the kanban boards for work tasks would have become more flexible.

It also provides new opportunities for analytics. Or here is the flexibility in creating tasks, for example, add an "analytics" task at the testing stage. For me, ooko is an experiment with a hierarchy of tasks, so what the pros or cons are remains to be seen. Something like that

Let me philosophize a bit: Stability gives you the opportunity to take the next step, diversity gives you the opportunity to choose a new direction.

Yes

What is a GP? I'm not a lawyer, so I wrote the license as best I could. If decompilation is needed only for auditing, then I have no objections, you can do it.

I think it's because the complexity of the tasks varies, and it's also difficult to predict this complexity.

In recent years, I've been working in 2-4 teams at the same time. Each team has its own manager, and every year one or two teams changed managers for different reasons. This gave me the opportunity to work with different people, but not a single case of successful introduction of WIP limits. It's not because someone didn't understand how to work with WIP. It just didn't have a permanent effect. For a change, it's worth trying different tools, I think it's useful for a good atmosphere in the team.

Perhaps you're right and it's worth changing the wording. But those users who are not ready to register will not follow the link and I will not find out about them. And those who are ready will not pay attention to the wording of the link.

Let's say. But is it good for the team? At a daily meeting, the manager shows the screen of his board and I don't understand where my tasks are on it. I've made personal filters for myself, but it's always difficult to navigate quickly in a meeting when it comes to my field of work

The limit can be specified per board (process). This is my vision of an electronic kanban board. Perhaps in the future I will add an indication to the columns, but now I want to check my guesses.

Using vibe coding, you will not be able to do such a service in such a short time. In addition to the goal of researching my kanban vision, I also experimented with an architecture that allowed me to achieve the required productivity and ease of development. AI is not that cool yet

Yes, registration is required. This is both a demo and a working service that is used by a dozen teams.

It takes most of the time to decide what to do next. I don't have so much energy and desire to do anything to try to do everything. The main way of promotion is advertising in search results. For me, it is the most effective and affordable in terms of quality for new users.

Trello does not work in Russia. You cannot install it on your server in the company's closed loop. There is no task number, there are no subtasks, you cannot see the progress of subtasks on the parent's board. There is no analytics. There is no page where you can view all the tasks that can be taken on. The service does not claim the laurels of solving all problems, but it is unique in its own way.

Yes, many people disagree with me. Take this as an assumption that I'm checking in my service. Of course, it is necessary to limit the amount of work, but in my opinion, WIP per column does not work. Therefore, I have implemented limits only for the entire kanban board (process).

ooko.pro It's not just a demo, it's a working service and a lot of people use it every day. The presence of registration is both a necessity and a kind of barrier from disinterested users.

I understand what you mean, but I think this is a self-deception of control. After thinking about it, I implemented WIP on the process (board), but only in the form of an "excess indicator".

I'll think about your words, thank you.

you can run it in a virtual machine. All the code is written in javascript, and you can study it without even decompiling it.

I do the service alone in my free time. Documentation is my weak side, it takes time, desire and understanding of what should be there. I am from Russia and most of the users of the service are from Russia. This is the first time that so many non-Russian speaking users have signed up for ooko. Telegram has translation functionality, if anything.

I do it alone in my free time. NPM is the easiest way to publish an application. You can install the app locally at your place. And there is also a TG channel, there are posts on the functionality for review.

I can't afford a free license. I have no sponsors and have been unemployed for a year. It's rare for a free-source project to succeed, so I decided not to use a free license initially.

"WIP" does not work - it only seems that you are in control of the process. It may work for the same type of tasks (hammering a nail), but in my practice, where all tasks are different, it did not work anywhere.

Usually, everything is set up "for the manager"—the way they prefer to view the project. As a result, a tool that is supposed to help the team becomes a burden. When you work across multiple teams, the constant filtering and scrolling turn into a nightmare. You waste your energy fighting the interface before you even start working. I believe that one glance at the board should be enough to instantly see where we are, who is overloaded, and what is stuck. That’s why I’m building ooko. To finally make the board a tool for the entire team.