• 1 Post
  • 141 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle

  • vscode with the built-in Emmet support.

    Emmet isn’t intimidating, unless you don’t know CSS, in which case it is extremely intimidating.

    a+b:
    <a href=""></a><b></b>
    
    a>b:
    <a href=""><b></b></a>
    
    a*2:
    <a href=""></a><a href=""></a>
    
    div.yeet:
    <div class="yeet"></div>
    
    A combination:
    a>b+i*2.dollah:
    <a href=""><b></b><i class="dollah"></i><i class="dollah"></i></a>
    

    That’s 99% of what you need to know to get started with Emmet.

    Anyway, I used to write 100% hand-written HTML, but switched to using Hugo because: Go’s built-in Templating language I knew from working with K8S, build-times are sub-second, and I can write a page in either Markdown or HTML, whichever I need (or even mix in some HTML in the Markdown!)

    Because of hugo I don’t need to mess around with repeating parts (like the nav menu).

    Only downsides:

    • it strips the comments, which I would’ve loved to leave in for people to read
    • the formatting is my favorite, so I format with prettier before committing

    I use git submodules to have the public/ folder be my Github Pages host repo, so I can just muck about locally, while I do a rebuild (which changes the files in the submodule). Only after a commit, I’ll effectively publish the website.

    Check out the website (mostly for the HTML - the articles are… meh): https://thaumatorium.com/ (no trackers, so no Cookiewall nonsense either :D)







  • I did a “game design” school when I was younger, but couldn’t get a job as a programmer. Worked for a laboratory for a little over a year, and then went back to school to get a software engineering degree. I was 28 when I went into it, worked with “youngsters” of 18 years and older. It was completely fine.

    I’m now 50k in debt, but I’m also making twice as much as I did with my minimally paying job at the laboratory. It’s going to be a boon in the long run, IMO.

    Then, luck should be taken into account. Once you are done with your degree, perhaps the market will have recovered a bit, because I’m hearing a lot of negative feedback lately.

    edit: If you’re not sure, you can take a peek at this graph of free MIT YouTube courses. Choose something interesting on the right, then figure out where to start on the left to get to your chosen point. Each course can easily take about 100 hours, which sounds a lot, but if you do them you can take that knowledge and more easily extrapolate information in the future.









    1. let pyproject.toml track the dependencies and dev-dependencies you actually care about
    • dependencies are what you need to run your application
    • dev-dependencies are not necessary to run your app, but to develop it (formatting, linting, utilities, etc)
    1. it can track exactly what’s needed ot run the application via the uv.lock file that contains each and every lib that’s needed.
    2. uv will install the needed Python version for you, completely separate from what your system is running.
    3. uv sync and uv run <application> is pretty much all you need to get going
    4. it’s blazingly fast in everything

  • pip3 freeze > requirements.txt

    I hate this. Because now I have a list of your dependencies, but also the dependencies of the dependencies, and I now have regular dependencies and dev-dependencies mixed up. If I’m new to Python I would have NO idea which libraries would be the important ones because it’s a jumbled mess.

    I’ve come to love uv (coming from poetry, coming from pip with a requirements/base.txt and requirements/dev.txt - gotta keep regular dependencies and dev-dependencies separate).

    uv sync

    uv run <application>

    That’s it. I don’t even need to install a compatible Python version, as uv takes care of that for me. It’ll automatically create a local .venv/, and it’s blazingly fast.