QuizzaciousOtter

Wow, thanks for posting this. I actually considered switching to PieFed because people say a lot of good things about it but now I know I won't. I can't treat codebase like this seriously.

When I was choosing an e-reader for myself some time ago I bought both PocketBook Era and Kobo Libra.

Kobo asked me to create an account during the first boot which I hated and that was pretty much it for Kobo. Now, I'm not saying this is unskippable because I honestly don't remember the details but somehow this made me not like it.

PocketBook has an awesome build quality. Certainly better than Kobo. It feels very premium and durable despite being pretty slim and I'm not afraid of throwing it into my backpack (with flip cover). The lack of handle curvature (like in Kobo) may be a slight disadvantage in ergonomics but it makes the reader much easier to pack and carry around.

As for downsides, PocketBook's software is slooow. Just flipping pages is ok but switching books, jumping around or going through menus is just unbearably slow. Good news is that Koreader solves this problem completely. It flies and is better anyway.

In the end I'm very satisfied with PocketBook Era and I would buy it again but Koreader is a must.

That's true and a bit of a bummer but I think those videos are still great. I don't care that much who makes them as long as the quality is good.

Wait, why is this downvoted?

Exposing services to the internet is one thing. The other thing is that without really solid backup strategy you can just lose your files. Both concerns grow even bigger if you're dealing with not just your own data but also your family's or friends'. It's a real responsibility.

I think it would be great if more people got into self-hosting but you really need to learn some stuff before jumping in. A single mistake can cost you a lot.

It's beautiful.

Sadly I can't use keyboards with just 3 thumb keys due to typing in Polish which has funny letters that require an additional modifier key. It's a shame because it looks like this one actually has space for one more thumb key on each half.

Just wanna say that plantuml exists. Despite its name it can be used for more than just UML. I know nothing about D2 though (yet) so can't tell how they compare.

I would say it does not. Well, I guess it depends on what you watch. The stuff I subscribe is nothing like TV.

curl is obviously fantastic but for more complex ad-hoc requests I usually prefer httpie.

As a dev, I can feel how much easier to work with the codebase must be after migrating from scattered raw SQL queries to ORM. In my job I have a project with a similar problem and the transition is slowly going on for years at this point, still not close to being finished.

I think Linkwarden is fantastic but should be described and advertised more as internet archiving software than a bookmark manager. It really should be obvious to anyone that it's downloading the webpages, not just saving links. I

I second this. Very light, feature-rich, configurable and works flawlessly. I use it for ad blocking, proxying all DNS requests to DoT upstreams, and local addresses in LAN and over Wireguard.

3 is not related to using git in any way. I'm not really sure what you mean in 4. I didn't mean making a lot of changes, I meant that you should not wait with committing until you have a finished feature / fix / whatever. Commit after each refactor, commit after adding a new testable unit. It's always better to have more checkpoints. If your team does code review, they will appreciate atomic commits too.

Use git for any code you write. Yes, even a simple script.
Commit and push often. More often than you think is reasonable. You can always rebase / fixup / squash / edit but you can't recover what you didn't commit.
???
Profit.

Seriously, once you commited something to the repo it's hard to lose it. Unless you delete .git. But a this point frequent pushing has your back.

I know git can be hard to grasp in the beginning. It was hard for me too. I highly encourage everyone to put in the effort to understand it. But if you don't want to do that right now just use it. Just commit and push. It will pay off.

Following tutorials and courses is definitely a very popular way of learning programming but I personally hate it. For me, the motivation was always a problem to solve, and programming was just a tool to solve it. Of course, you probably need to follow some kind of guided experience to gather the absolute fundamentals, but to get better you just need to apply this in practice.

The first ever problem I decided to solve with programming was organizing pirated video files into manageable directory structure. I knew almost nothing about programming at this point and my thought process was something like this:

Which programming language should I use? Search the web, read a bunch of articles, make a decision. I chose Python.
Ok, first I need to find the files to process. Search the web for "get files in a folder Python". Read a bunch of answers (never just a single one!). Apply the solution.
Now I need to somehow discern between movies and series episodes. Search the web for "check if text contains text Python".
Repeat until you have a working program...

Now, the most important part of this is to have an idea for a project which either solves a real problem of yours or just is exciting to you. Some examples of my projects:

Due to weird grading system used in my school, calculating GPA was pretty inconvenient. I decided to solve this with programming. I wanted to make the solution easily available to my teammates so I created a web app.
I wanted to control my smart TV using a computer. I knew it can be controlled using Android application so it seemed likely that I can do the same using my PC.
I bought a smart lightbulb and I was playing with setting it to different colors while listening to music. A thought suddenly popped up: "hey, can I make it blink to the music?".

When starting most of these projects I had no idea how to approach the problem. So I just searched the web until I knew it. In the beginning you will probably be searching and reading much more than writing code. But that's a good thing! Programming (or rather software engineering) is not about typing out code, it's about breaking down the problem into smaller chunks until you actually know how to solve each of the chunks with the tools you have at hand. Once you have this understanding, writing code is usually rather easy.

I always wanted to play with those cool pipettes you see in lab stock photos and videos. I don't even know why but they just seem so cool.

Yes, that's why I'm asking questions and not bashing this person for using an LLM.

How could you catch hallucinations without checking this information with another source? Or is it the case that coming up with a correct search phrase was the hard part so when you already had the explanation it was easier to search for it? But at that point quoting the other source instead of LLM would be the obvious choice for me.

I'm pretty this applies to tram and bus drivers literally everywhere.

QuizzaciousOtter

@ QuizzaciousOtter @lemmy.dbzer0.com

Posts

1
Comments

67
Joined

1 yr. ago

QuizzaciousOtter

Fun fact: you can't upload this image on piefed.social

Permanently Deleted

Permanently Deleted

Stop cramming everything onto one Pi: treat your home lab like a tiny ISP - hardware, stack, backups and an update plan

Is self-hosting becoming too gatekept by power users?

Toucan Wireless Split Keyboard with Touchpad

What open source project is the most exciting for you right now?

D2: Diagram Scripting Language

Anyone else not watch movies or TV shows?

Just use cURL

Jellyfin 10.11.0 Released

Linkwarden downloaded the whole flipping Internet ...

Beyond Pi-Hole

Well well well.

Well well well.

How exactly does one get better at programming?

tag yourself

haemogoblin

haemogoblin

🖐🏻🖐🏻🖐🏻