pcouy @ pcouy @lemmy.pierre-couy.fr

Posts

24

Comments

162

Joined

2 yr. ago

For anyone who wonders, this is related to cryptocurrencies

Thanks for the detailed feedback! I made an attempt to put settings that change between environments in a separate file, I'll try switching to environment files.

Regarding secrets, I'd love to integrate with a secret management solution, or even better, turn the whole thing into some ansible stuff (which I never used but seems awesome). Do you recommend anything on this side?

Thanks for the detailed answer about your learning experience and for the link 👍 ! I'll make sure to check it out.

Thanks for the suggestion, I cross-posted to these two communities.

Regarding Docker, I actually made two compose files : one for quickly getting a dev env running, and another one for deploying to (pre-)production.

I am not an actual teacher, I only supervise practical computer science work aside from my dev job, so I have no saying in what is taught. But don't worry, this is only a very basic introductory course, no factories, not even inheritance. Only classes, attributes and methods.

Lol I almost fell for it. I just Ctrl+F'd the link, no occurence of "tab" in the press release :D

Do you mind sharing links to the courses you found ? I've been teaching Java to students who almost never wrote code before, and I'm always looking for beginner-friendly resources I can recommend to them.

I had a great time using Qubes. It made me learn about the Xen hypervisor and CoW filesystems.

However, if OP complains about build times being too long on their CPU, I'm not sure they will get Qubes running smoothly on the same hardware. I'm especially worried about every VM besides dom0 being software rendered.

I can think of some "programming best practices" that can help with reducing merge conflicts, such as making small functions/methods, but I see it as a positive side effect.

I don't think avoiding merge conflicts should be a goal we actively try to reach. Writing readable code organized in atomic commits will already help you get fewer conflicts and will make them easier to resolve.

I've seen too many junior and students being distracted from getting their task done because they spent so much time "coordinating" on order to avoid these "scary" merge conflicts

That was the point of my comment, unless they wrote this ironically.

Sorry you went through the trouble of writing all of this explanation, I hope this is useful to someone else

How do you avoid conflicts happening in the first place?

Might as well use Google drive... Or maybe actually learn to use git? The learning curve is steep but it's worth investing in it

Well, it kind of makes sense to give a figure in such an unit. It allows you to quickly calculate how much you're gonna spend on your electric bill (but only if you're based in the US), since all weird conversions are already done

Well, Watts are just a different way to write Joules per second. The unit we should eliminate is {k,M}W.h which introduce a 3.6 factor in conversions to/from the regular unit system

Nice paywall :/

Github is not really independent from Git, it's a git provider. (you could see it as Github being to Git what Gmail is to e-mails)

Each time you send a packet over the internet, several routers handle this packet without touching the source and destination IP addresses.

There is nothing stopping him from configuring the VPS in a way that forwards packets from the home server, rewriting the destination IP (and optionally destination port as well) but leaving the source IP intact.

For outgoing packets, the VPS should rewrite the source (homeserver) IP and port and leave the destination intact.

With iptables, this is done with MASQUERADE rules.

This is pretty much how any NAT, including ones behind home routers, work.

You then configure the homeserver to use the VPS as a gateway over wireguard, which should achieve the desired result.

I totally agree with w3schools being bad. However, when teaching web dev to beginner students, they usually find the MDN hard to understand and turn to w3schools.

The MDN requires either quite a lot of experience reading documentation, or being shown how to navigate it.

What do you mean? Are you talking about the hash being spoofed?

Not so long ago, while trying to turn a side project of mine into a package, I bind mounted my home directory into a chroot.

Guess what happened when I rm -rfed the chroot...