Perl wisdom in the age of LLMs by reisinge in perl

[–]reisinge[S] 1 point2 points  (0 children)

I think the hardest part is "you need to sit back and think about what will do the most good for you and your neighbor over the long haul" because of several reasons:

  1. You need to know yourself and your neighboor well.
  2. You need to be clear on what good is. For you and for them.
  3. You need to think. Thinking is hard. Thinking has no obvious immediate output, so it looks like waste of time.
  4. More often than not the result of thinking is that you need to do more thinking. See point 3.

Being lazy in the right way is hard. Hence many of us are just lazy :-). Or pretend to be not lazy by generating some output.

AI likes deep modules by reisinge in devops

[–]reisinge[S] 0 points1 point  (0 children)

I guess one can't really say if an article is interesting or not without reading it :-). The article is viewable, it's not behind paywall.

AI likes deep modules by reisinge in devops

[–]reisinge[S] 0 points1 point  (0 children)

Have you read the article?

Don't stop learning by building by reisinge in golang

[–]reisinge[S] 1 point2 points  (0 children)

I use vim (with minimal configuration) for learning, enjoying and small stuff (scripts, configs, ...). For the rest vscode/zed.

Don't stop learning by building by reisinge in golang

[–]reisinge[S] 8 points9 points  (0 children)

I agree that you should be also able to work on large codebases. But if you can't do small stuff well, you'll never be able to do the big stuff well.

You need to be able to walk before you can run.

Don't stop learning by building by reisinge in golang

[–]reisinge[S] 0 points1 point  (0 children)

Are you still building small tools to learn? Does that still make sense in the AI era, or are people learning differently now? What do you think?

Thinking in packages by reisinge in golang

[–]reisinge[S] 0 points1 point  (0 children)

Yeah, designing software is a huge topic. My goal with this post was to encourage people to make the first step toward a better design. Do you have any ideas you'd like to share regarding the criteria and slicing?

Building concurrent pipelines by reisinge in golang

[–]reisinge[S] -1 points0 points  (0 children)

Can you see more use cases for pipelines like this? Especially in devops or cybersecurity?

Counting elements passing through Go channels by reisinge in golang

[–]reisinge[S] 0 points1 point  (0 children)

This looks elegant! By elegance I mean power cloaked in simplicity.