this post was submitted on 14 Feb 2025
38 points (100.0% liked)

Learn Programming

1726 readers
1 users here now

Posting Etiquette

  1. Ask the main part of your question in the title. This should be concise but informative.

  2. Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.

  3. Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.

  4. Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 2 years ago
MODERATORS
 

Learning by doing is hard to beat when it comes to building software.

I am starting a home lab to have a safe environment to try things out. Any ideas on what I could run that is completely useless but fun to set up?

@learn_programming
@homelabs

you are viewing a single comment's thread
view the rest of the comments
[–] logging_strict 2 points 1 week ago

Take any package that is no longer maintained and git clone it.

Configure the dev environment

  • pre-compile

  • three tox config files:

    testing, docs/lint/formatting/pre-compile/interrogate, update/sync requirements files

  • unittest --> pytest

    Read the tests and then bring it up to your current competency level

  • gh workflows

  • pyproject.toml

poetry is worthless!

If the build backend focus is on requirements and not build plugins, remove it. Use a separate package for requirements file management.

For how to do this see how logging-strict is doing it

https://github.com/msftcangoblowm/logging-strict

Specifically pyproject.toml and tox-req.ini