Isammoc

I love scala that does both greatly

Sadly, not enough diagram nor technical documentation at all. It's a thing that change over time, but there is a large gap.

About tooling, we have tried some mermaid, plantuml, or other diagram generated from source tool but really nothing that is satisfying.

I'm interested as well in this subject

I remember playing it on newsgroup. Good format (with threads and subthreads) and people using correctly actual convention. Too bad I don't see a running game anymore.

By chance! I was working in a company that needed a mail templating that could send a large amount (yeah... I learned it was spam alike after) And one of my coworker came with a solution of programming by actors with Akka actors, based on scala. So to help this coworker maintaining and evolving this application, I learn the language and the concepts under the language. Now I chose my current job partly for the language (and because there is a strong connection with open source contribution)

Really, for my job, it depends on the subject. Next feature: the CTO (small structure, so he has the PO cap). Small library dependency to add in our project, the dev that need it. Big refactoring: the one that had the idea validated by the whole team (to be sure it's the path we want to take). Process/documentation: a team specific meeting. Usually, small nits to change to sustain all team members. For current next big feature, it's the fourth proposal and we don't agree yet. So was have more proposals to come.

Title and site are unrelated.

A configurable optional footer with source code link to anywhere.

License in the footer as well (perhaps more difficult to change if the license is copyleft)

As any open source (that want contributors and/or forks), a full readme, a quick start, a contribution guide, a documentation, etc.

I don't understand why "title"s are so partitioning?

Obviously, the PO is accountable for the user stories, but they are not to write them all by themselves.

Let the PO decide what is the next big feature, then pair them with a dev to split into manageable stories. Such stories will be then smaller and still have to be split in task. But at least, the user story will be small enough to be develop as is.

PO will have the last word about the big picture and the details (user facing) but the means are in dev hands.

I won't work anymore for a company than ask me to work without being able to install the tools I need to work.

Current work sent tech employees a blank computer and any licenses we ask. So basically, you'll have sudo if you install it.

On the other hand, we are often reminded to upgrade our stack / to check if we have been compromised, etc.

The whole purpose is the pureness of your component.

When react executes your component function, it will initialize a context (a big array) and each hook will be linked to an index in this context.

So, while being nearly pure, we can describe side effect but only for the provided context.

I have a graveyard full of such personal projects.

In another hand, if you are still maintaining this project, it can be interesting to refactor it and show your process doing it. It can be a great way to show actual useful skills for a future interview or, at least, train to do so before actually using it in a real production project.

Refactoring to a state of the art state while the project is still under development and shipped can be a valuable skill to train and show.

My opinion: first versions of an app is often written as PoC, without any test. It requires real data (file, db, working external API) and only "works". Because at that time, we (developers) know what should be done and how. Then come users who will define their own stories, where TDD is the best but... it is now hard to test.

Congrats! From the landing page, I miss some information: * will it be always free? (I guess not) * what do you do with my email? (Only for login, or do you sell it) * will my data be mine or do you own it?

I understand that it is a MVP, but I cannot put job real data without warranty.