I’ll say, one thing that helped me here was starting to see the “depth in the breadth”, so to speak, and recognizing this jumping around for what it was. A lot of novelty seeking and bouncing between hobbies to avoid conscious regulating, which was tiring.

Now, in things that I consider important, I try to find the novelty and breadth that comes with sticking to it for a long time - stare at a hobby / occupation long enough to see the big world inside of it and realize it’s more than you can take in and take time to put up some blinders so you can hone in there and see it as lots of cool novel things within a smaller space.

Also, realizing that bouncing around to all kinds of things… well, that’s my form of relaxing. If I’m totally depleted, chances are what I need isn’t to sit in one place and “rest”, or to focus on one thing, it’s to schedule time to completely not focus on one thing and allow myself to bounce all over the place and do whatever feels good (within responsible limits). It’s usually a chaotic mess that amounts to no long-term benefit, but it’s much more resting that trying to relax. Trying was the problem, after all.

Yeah, this is the approach people are trying to take more now, the problem is generally amount of that data needed and verifying it’s high quality in the first place, but these systems are positive feedback loops both in training and in use. If you train on higher quality code, it will write higher quality code, but be less able to handle edge cases or potentially complete code in a salient way that wasn’t at the same quality bar or style as the training code.

On the use side, if you provide higher quality code as input when prompting, it is more likely to predict higher quality code because it’s continuing what was written. Using standard approaches, documenting, just generally following good practice with code before sending it to the LLM will majorly improve results.

Yeah, I knew freelance folks who provided long term support with such complicated setups. The base daily rate plus hourly with a monthly retainer and weekly on call fees. Wild.

Or, hourly = extremely high paid contract work.

When I teach story points (not in an official Agile Scrum capacity, just as part of a larger course) I emphasize that the points are for conversation and consensus more than actual estimates.

Saying this story is bigger than that one, and why, and seeing people in something like planning poker give drastically differing estimates is a great way to signal that people don’t really get the story or some major area wasn’t considered. It’s a great discussion tool. Then it also gives a really rough ballpark to help the PO reprioritize the next two sprints before planning, but I don’t think they should ever be taken too seriously (or else you probably wasted a ton of time trying to be accurate on something you’re not going to be accurate on).

Students usually start by using task-hours as their metric, and naturally get pretty granular with tasks. This is for smaller projects - in larger ones, amortizing to just number of tasks is effectively the same as long as it’s not chewing away way more time in planning.

I know this post and comment might sound shilly but switching to more expensive microfibre underwear actually made a big impact on my life and motivated me to start buying better fitting and better material clothes.

I’d always bought cheap and thought anything else was silly. I was wrong. So much more comfortable, I haven’t had a single pair even begin to wear down a little bit, less sweating and feel cleaner, fit better, and haven’t been scrunchy or uncomfortable once compared to the daily issues of that cheap FotL life. This led to more expensive and longer lasting socks with textures I like better, better fitting shoes that survive more than one season.

It was spawned by some severe weight loss and a need to restock my wardrobe. My old underwear stuck around as backups to tell me I needed to do laundry, but going back to the old ones was bad enough that I stopped postponing laundry.

Basically, I really didn’t appreciate how much I absolutely hated so many textures I was constantly in contact with until I tried alternative underwear and realized you don’t have to just deal with that all the time.

It depends what “From Scratch” means to you, as I don’t know your level of programming or interests, because you could be talking about making a game from beginning to end, and you could be talking about…

• Using a general purpose game engine (Unity, Godot, Unreal) and pre-made assets (e.g., Unity Asset Store, Epic Marketplace)?
• Using a general purpose game engine almost purely as a rendering+input engine with a nice user interface and building your own engine overtop of that
• Using frameworks for user input and rendering images, but not necessarily ones built for games, so they’re more general purpose and you’ll need to write a lot of game code to put it all together into your own engine before you even starting “Making the game”, but offer extreme control over every piece so that you can make something very strange and experimental, but lots of technical overhead before you get started
• Writing your own frameworks for handling user input and rendering images… that same as previous, but you’ll spend 99% of your time trying to rewrite the wheel and get it to go as fast as any off the shelf replacement

If you’re new to programming and just want to make a game, consider Godot with GDScript - here’s a guide created in Godot to learn GDScript interactively with no programming experience. GDScript is like Python, a very widely used language outside of games, but it is exclusive to Godot so you’ll need to transfer it. You can also use C# in Godot, but it’s a bigger learning curve, though it is very general and used in a lot of games.

I’m a big Godot fan, but Unity and Unreal Engine are solid. Unreal might have a steeper learning curve, Godot is a free and open-source project with a nice community but it doesn’t have the extensive userbase and forum repository of Unity and Unreal, Unity is so widely used there’s lots of info out there.

If you did want to go really from scratch, you can try using something like Pygame in Python or Processing in Java, which are entirely code-created (no user interface) but offer lots of helpful functionality for making games purely from code. Very flexible. That said, they’ll often run slow, they’ll take more time to get started on a project, and you’ll very quickly hit a ceiling for how much you can realistically do in them before anything practical.

If you want to go a bit lower, C++ with SDL2, learning OpenGL, and learning about how games are rendered and all that is great - it will be fast, and you’ll learn the skills to modify Godot, Unreal, etc. to do anything you’d like, but similar caveats to previous; there’s likely a low ceiling for the quality you’ll be able to put out and high overhead to get started on a project.

Yeah, I really think it’s important to not see Lemmy as one singular community, or a lot of important use cases will go ignored.

Not the OP, but in Canada at least, I think you would legally be expected to because common law is (as far as I’m aware) very nearly marriage and is entirely implied by time living together in a conjugal relationship. It might be provincial to determine the actual property laws, though.

I don’t have a firm opinion here, but I think the key difference in your case is that a conjugal relationship has some expectation of… Oh I don’t know, mutuality? A landlord tenant relationship is a lease agreement. If your roommate didn’t sign any kind of lease agreement, they might have a legal case to just not pay you and suffer no consequences (I don’t know), but they’re not in a conjugal relationship, so there’s also no implication of shared ownership.

Without signing lease agreement and being in a conjugal relationship, I think there is a pretty fair case that expecting shared ownership is a fair assumption.

That all said, it’s also really up to the individuals to figure that out early, and the deception in the meme suggests that the agency to have that discussion wasn’t available, and that’s really the part I find problematic here.

That and expropriation/eminent domain, etc. Even if you pay your taxes, if the government needs it, they have processes to take it.

I’m not saying it’s an inherently bad thing, but it’s another one of those important things to realize is already present if anyone wants to argue for/against certain government reforms.

I know it’s controversial, but moving away from “guys” when I address a group and more or less defaulting to “they” when referring to people I don’t know.

They was practical, because I deal with so many students exclusively via email, and the majority of them have foreign names where I’d never be able to place a gender anyways if they didn’t state pronouns.

Switching away from guys was natural, but I’m in a very male dominated field and I’d heard from women students in my undergrad that they did feel just a bit excluded in a class setting (not as much social settings) when the professor addresses a room of 120 men and 5 women with “Guys”, so it just more or less fell to the side in favour of folks/everyone.

Getting really speculative, but maybe Infinite Scrolling and similar UX design patterns. I think we learned it was dangerous pretty early in, but I have a feeling there isn’t currently a widespread understanding of just how badly things like infinite scrolling shortcircuit parts of the brain and cause issues with attention and time regulation in large populations.

If I was more researched on it, I might include infinite short-form content feeds of almost any type to be honest, which may just be another way of saying social media.

Conversely, if smart watches with accurate health monitoring become cheap and commonplace it might drastically improve health outcomes by motivating people to see doctor’s when needed for subtle heart issues that would otherwise go unchecked.

“Where did you learn this skill?” “The olde rules prevent me from discussing this further.”

Foul Bachelorette Frog caused some real uncomfortable and eye opening ruckus for a lot of folks.

My bones are tingling.

In Canada, we play this game where we complain that all employees (aside from “contract workers” in gig work) make minimum wage and don’t live off of tips like our American counterparts, then someone complains that minimum wage still isn’t livable so tips are still important, then someone retorts that this only means everyone in minimum wage needs tipping or nobody needs tipping, which usually ends up in a lot of poop being slinged around until you get guilted into tipping before receiving any service.

This mouse? Believe it or not, file.

Yeah, I think framing it similar to the old days might help, but I could be wrong. Like, you aren’t signing up for (just to web-equivalent) PHP Fusion or something, you’re signing up for your gaming clan’s forum, or your roleplay group, or your Canadian phreak BB. The difference with Lemmy is just that you also indirectly sign up to receive content from a lot of other places using the same protocol.

IMO, I think the framing/abstraction will make or break the future of the paradigm for mainstream consumption. Not to get into another repeat of the EEE discussion, but assuming nothing nefarious from something like Threads, that would mean people start an account there and then find a niche group with their friends to go hang out on instead.

I also have to push back against the pushback against the paradigm going mainstream, because again IMO a move back toward decentralized platforms is really important for the future of the internet and quite frankly the global economy.

Just editing to expand, but I think maybe there’s a problem in framing Lemmy or Mastodon as communities in themselves, because it really conflicts with the model of instancing and email that is being used to describe them.

Same! If you know of any online courses suitable for postsecondary students looking to build tech skills I would appreciate it, otherwise I might need to try getting a duty reallocation for a bit to put time into building one.