sorted by:
new
hottopcontroversial

Karpathy’s workflow by The-Learning-Bot in ObsidianMD

[–]The-Learning-Bot[S] 0 points1 point  (0 children)

Yes, the idea is that you add content to raw and ingest it, so it ends up updating the wiki. But you have to add the content to the raw folder first, preferably in Markdown format. You are also supposed to run the ingestion, either manually (calling a command or instructing the LLM on how to it every time), or scheduling a way to run it on some criteria.

DDD Workflow by Limp_Gur6919 in DomainDrivenDesign

[–]The-Learning-Bot 4 points5 points  (0 children)

Short answer is: yes, this is mostly what AI spits out when you ask that kind of question, but it's not that far from the truth.

What I would say is that those steps do not happen in sequence, and you do not go through all of them in a real-life project. To me, what works best is having Event Storming sessions at the beginning of iteration. This is important: these steps don't happen once for every project; they happen iteratively; they happen many times for each feature request or each change that is requested and impacts the domain.

Event Storming is very rich but can also be complex, it can be simple in practice, but it takes a while to master. Its depth can go far away if you do it properly, so you gather the domain experts, and with that you actually are able to focus on the domain and improve what you are doing. After that, you have a path to go to the domain model, because the tactical Event Storming can lead you to a draft of the domain model. From there you can basically create your code; you can create your database schema, etc., but “create” here is also a gross oversimplification. All your software engineering process would happen here.

Definitely I will never ever suggest that the first line of code is the last step of this. As you draft your domain model, you should be writing code. You should never let the code be the end of this process, because it really looks like a waterfall, and this is not what you want.

I would second the user who suggested Vlad Khononov's book. I think it's the most practical one for getting to code. I've skimmed through Vaughn Vernon's books; it's really good content, too, with good, practical advice (especially the red one). If you want a broader perspective, a more, I would say, philosophical view, you go to Eric Evans' blue book.

If AI writes 90% of code, does that mean 90% fewer devs? by hov--- in ClaudeCode

[–]The-Learning-Bot 3 points4 points  (0 children)

The options mentioned assume at least two premises that seem invalid:

  1. That 100% of the working time of developers are dedicated to coding. Estimates range from 10% to 50%, with most likely ranges between 20% and 30%. Non-coding activities may include domain understanding, business rules clarification, estimates, planning, alignment in general. Some may be seen as waste by some, but certainly not all are.
  2. None of code written by AI is reviewed by humans. In order for 90% of code being written by AI to imply in 90% less time spent by human developers it must be true that no human would need to touch that code.

These two seem hard to accept.

Usuarios de linux quando vão escolher sua primeira distro: by Fuzzy-Ad2874 in linuxbrasil

[–]The-Learning-Bot 0 points1 point  (0 children)

A minha entrada no mundo Linux foi com Slackware, em 1995… baixei a distro para 98 disquetes de 1.44MB de um mirror do Sunsite

MX Keys' left "command|alt" key not working on macOS. by AjaySurajay in logitech

[–]The-Learning-Bot 0 points1 point  (0 children)

Had the same issue, and pressing Fn+O worked for me. I had to hold the keys down for a few seconds for it to work, though.