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?
Learning by doing is hard to beat when it comes to building software.
2 years ago by rissanen to c/learn_programming
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?
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
home is not a safe environment. Might be possible with alot of preparation like sound proof and a lock on the room.
The entire point of all the security is to protect yourself from the wife unit
I code at a cafe. Far far far away from interruptions.
@logging_strict We might have different things in mind when we say safe.
Moving to a place for deep work sounds like a good idea indeed!
i'm deadly serious. A cafe isn't silent, just are left alone to do our thing
@programming.dev
Ask the main part of your question in the title. This should be concise but informative.
Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.
Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.
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
go to feed...
@programming.dev
Ask the main part of your question in the title. This should be concise but informative.
Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.
Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.
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
go to feed...
Checkout awesome self-hosting lists.
save