pixxelkick @ pixxelkick @lemmy.world

Posts

3

Comments

543

Joined

2 yr. ago

Because everyone knows people all just stopped buying houses between 2019 and 2024 lol.

Do you think people are poor simply because they’re too dumb to think “I should spend less money on groceries?”

It's usually spending money poorly, yes. But I don't blame them, I blame the lack of education on these topics.

If you aren't even using freely available budgeting options, then I recommend to start there and assess spending.

I very rarely encounter people who complain about money but also have real concrete budget. If I ask it's usually met with excuses and changing the topic.

If you truly have a genuine budget and still can't figure out where the money is going, then it's a more serious chat.

But the absurd frequency you see people posting about how they can't afford groceries and lo and behold, they're buying a bunch of overpriced garbage and paying extra for non necessities, it's bananas.

If you complain about food costs and I find out you don't know how to break down a whole chicken, I feel a little less bad for you.

If I find out your buying dumb shit, my empathy starts to go down.

I lived with and worked in a poverty stricken industry for many many years, and the constant frequency I saw people complain about money one day, then waste money the next, has gradually over time led me to just assume most people are completely inept when it comes to budgeting.

And I mean, it's not exactly a required course in high school, so I am not that surprised.

And it's mostly food, drugs, and alcohol when it comes to wasting money.

That and the "buying little things you dont need thatll end up in the trash" I see often. Fast fashion and all that jazz.

It's a serious problem honestly.

Doesn't even need to be middle of nowhere. Just needs to be ~30 minute drive away from city core. Cheaper suburbs are still very much affordable in every city I have seen.

Sometimes you gotta go out to that 20-30 min away "next nearest" smaller town that's right next to the big city but isn't actually in it. It has all your amenities and plenty to live off of, but if you wanna go to the big city's malls, theaters, concerts, etc, you gotta drive 30 min instead of walk there.

Usually you can get very decent starter homes for 250k to 300k in said places, and usually in said "one off" towns the renting industry is much more slow, so you don't have that "you have to buy NOW" pressure. Homes stay up for sale for a bit and you have more than 3 hours to make an offer lol.

Downside is now you need a car... though often even then the smaller towns have some form of public transport to the bigger city you can use, though it can be on a rarer schedule. IE your bus may only come every 2 hours so better not miss it.

I prefer "edge of the city suburbs" over "one town over" personally. Access to public transport means I skipped buying and paying for a vehicle and skipped straight to saving up for a house.

There's not really a nice way to frame "your post sounds like it was written by an extremely cringe teenager trying to cosplay as their idea of what constitutes a professional dev, demonstrated by the classic combination of ignoring everything prior written, attempting to represent a ball of mud as a badge of honor, and unironically trying to use lines of code count as a metric to measure by"

Literally checked off all the "lol sure bud" boxes in a single statement, and then if you aren't picking up on the nuance, let me explain what I wrote after:

I hope you understand later how incredibly cringe what you wrote is, because the day you do is the day you have likely matured enough in knowledge and skill to call yourself a professional unironically, which is a good thing.

Until that day, stop prostrating shit like what you just wrote above if you ever want any developer worth their salt to take you even remotely seriously, otherwise you will likely find yourself the laughing stock very quickly of any serious circle.

Best of luck out there, and finally:

Next time someone is giving extremely useful advice, just write it down, don't shit talk. That's without a doubt the #1 divergence that separates the path between long term failure vs success.

Everything about what you just wrote, and the way you represented it, signals you are precisely the type of individual that should take everything about what I wrote above very much to heart, friend.

If you have no idea what I'm talking about, I hope one day you do :)

If you haven't played it yet, OP you may really like Ultros.

Classic feeling metroidvania, modern game engine, but it's visuals are fucking amazing and the colors, oh man.

They went for this incredible psychedelic art style and it's just gorgeous and vibrant.

https://youtu.be/AyGZAzHu1QQ?si=AdEjVo3pjHZ-MuFn

That’s code review.

Only on very small projects.

As the team grows, having just 1 person review your code is simply not sufficient.

Even 2-3 may not be enough to sanity check if a larger new feature on a massive project is good. If it impacts the team and means a fundamental shift in methodology, then you need more voices weighing in.

Now, can you merge the PR in first, then have the meeting after? Sure, I guess, but why would you?

If the team reacts negatively to what you built, finds flaws in it, or simply just doesn't get it because you overengineered, now you have to revert the PR and go back to the drawing board.

It makes tremendously more sense to bring folks impacted in on a swarmed live PR review as you go over what you did, where you did it, and why... before you merge it in.

At this point you can QnA, get suggestions, feedback, etc.

Now typically most of my response to live chat feedback is "aight, can you add that as a comment on the PR itself so I can see it after?" And then they go and do that asap, usually typing it up as I answer other folks questions. Because at this stage the PR is literally the perfect place for feedback to go.

I've been down the path of "1 person LGTMs the PR, huge new feature is added, I document it on the wiki rigorously, I post the new feature to chat... 1/10 people bother to use it and 9/10 give blank glassy stares when I bring it up"

It. Doesn't. Work.

Period, lol. And don't get me wrong, I wish it did, but people just don't RTFM mate, that's a fact of life a d the sooner you accept that, the easier the job gets.

it’s rare that a single PR introduces anything but a small slice of a feature

Yes, I never said this was a common occurrence. This is indeed rare but it dies happen.

And we’re not really talking about a PR review at this point

No, this is 100% still part of the PR review, I was pretty explicit about that. This process should happen for a large feature/service/etc as this simply cannot be covered by a "LGTM!" Comment on a PR.

These meetings primarily cover when you've established something that needs to be followed or used moving forward. IE: "This new feature makes our lives a lot easier and now (annoying thing) is much easier to implement. This is how I used it in my PR and I wanna make sure all the rest of the team is on the same page about it, and everyone else starts using it in the future."

This 100% comes up here and there and it absolutely necessitates an actual meeting, because any dev worth their salt knows what happens if you dont get everyone on the same page on it...

The inevitable "why didn't you use (thing I made explicitly for this purpose)?" Convo comes up a month or two later, because all you did was document the new thing and open a PR, get a couple "LGTM!"s, and you posted a blurb about it in the chat and pinged some folks.

And if you've gone through this process before you will know that simply just never works, full stop. Doesn't matter the team, doesn't matter how well documented, doesn't matter how good your write up is... People. Don't. Read.

There's a reason "RTFM" is such a meme in linux communities, people don't fuckin read mate, abd that's why critical big PRs 100% need a 20-30 min QnA meeting so people can actually talk about it.

I'd estimate tops 10-20% of devs that should read your docs, will actually do it.

Do you not do demo meetings after introducing entirely new features?

Sometimes a PR can be quite large as it involves an entirely brand new feature that simply didn't exist before.

And if it's an internal tool/service for fellow devs to use to make their lives easier, yes, it likely deserves a meeting so the devs can have a chance to QnA about it. Usually 5-10 minutes going over the who/what/why/where/how, then 20 mins or whatever of any needed QnA if devs are curious for more info about specifics, like performance or extensibility or etc.

If you create a new tool like that abd then just hand it off with all the devs have to go on being "here's the manual, figure it out" you know what happens?

Almost no one reads it, and pretty much no one uses it, because parsing a giant manual of info is difficult co.pared to seeing a live demo

Anecdotal warning: From my experience going tk a gandful of schools in western canada... inner city schools bias towards women dimishes due to higher risk conditions. The gender ratio shifts as you go from nicer well funded schools to inner city poorer neighborhoods.

The higher risk schools tend to have way more men teaching as well as male cops walking around, whereas the gentrified safer schools tend to be women dominated.

It still leand towards women, but the lean evens out a lot more as risk/danger goes up, as well as pay.

You also see more male teachers if you go way up to far northern schools that have much harsher conditions, where governments trade to provide monetary incentives in return for roughing it up on way more secluded places.

So, nope, from what I've seen the pattern holds just as much in teaching.

Men work more overtime, take on more risks, and are more willing to put themselves in danger.

Men get paid more, because they are willing to pay the extra pound of flesh it demands, because they have a bit more flesh to offer. Men have higher average stamina, physical strength, and physical resilience.

I won't necessarily say that's a good thing, but it's a fact. There's a reason all the dangerous jobs are male dominated, but simultaneously men die on the job or get severely maimed substantially more.

Interestingly enough if you look at a woman dominated industry that is extremely dangerous abd demands a pound of flesh (like prostitution) suddenly the gender gap flips heavily the other way.

As I always say, you don't see people talking about gender disparity of garbage truck drivers and other areas of the sanitation industry, even though there's a lot of disparity over there.

Why aren't people complaining about the lack of women in the sanitation industry? Weird, huh?

to do nothing and blame genetics

You are doing the same, just a layer of abstraction and human constructing out.

Addiction, and the willpower struggle, are genetic. You are aware things like ADHD exist, yes? Abd that ADHD is genetic?

Willpower is inherent to psychological topology, which is an abstracted idea overtop of the physical makeup of your brain, which is heavily genetically influenced.

The other half is environment.

Primarily speaking, the combination of a poor environment (which most people suffer nowadays in the west) and a "bad roll" on genetics for what brain you end up with, and you become heavily predisposed towards addictive behavior patterns.

And while eating and obesity aren't the only addictive behaviors, of course, they are both legal and highly available making them very common.

What I'd be curious about is how you think "willpower" isnt genetic. Are you suggesting it's somehow an external force outside the human body...? That'd make no sense.

Largely speaking this sort of statement is just an attempt to discard establish science by just smothering a layer of abstraction overtop and pretend it's something else.

"Willpower" is not a quantitative established metric, OP. How do you measure it? How do you quantify it?

Dopamine exhaustion, decision fatigue, and executive function however are established concepts that are easier to discuss in a serious manner.

Would I agree that obesity has a comorbodity with poor executive function? Yes, 100%!

Would I say that executive function isn't genetic? God no, it's heavily genetic, when it is particularly bad that's literally called ADHD.

1. Make branch for the ticket
2. Make periodic commits to branch
3. Open PR from branch to main
4. (optional) if the changes are big, I have a meeting with devs to discuss it. If I can't easily explain to the junior devs what I did and why, it means I did something wrong.

As a senior dev, I've found "can the junior devs grok wtf I did/made" to be an excellent "did I overengineer?" Litmus test.

A good implementation should be not too hard to explain to the juniors, and they should be able to "get it" in a single short 20-30 minute meeting at most.

If they are curious/interested and ask questions, that's a good sign I made something useful and worthwhile.

If I get a lot of "I'm not sure I get it" and blank stares, I probably have overcomplicated the solution.

If that "ooooh, okay!" Comes quickly, then we are good!

I have been using Reolink RC-522s outside in the harsh Canadian cold winters. Even at -40 they kept working and their quality hasn't degraded.

I tried out q few options for NVR software, and I've settled on Frigate NVR, it was pretty painless to setup and "just worked".

Shinobi I found worked at first but three times it shit the bed, silently failed one day, and just stopped working. I'd wipe and re-install and it'd just fail after awhile. Frigate has never had this issue so far.

I use Power over Ethernet for the cameras, so i only had to run 1 single cable (ethernet) to each camera outside, no need to run high voltage which makes it way easier to install.

I use a small mini itx PC as the NVR with a 960ti installed in it for transcoding.

I have a fancy managed 48 port gigabit poe switch which is overkill for just cameras (I have tonnes of other PoE devices on my network as well justifying it), but any "dumb" gigabit poe switch will work for you, as long as you have enough ports for your cameras.

I personally use kubernetes for my machines running self hosted apps, but for most folks that's overkill abd you can just use docker compose!

In Canada the Cert and the Degree are separate.

You typically through getting your degree also become certified, but the key is while your degree lasts forever, the Cert has to be maintained and renewed.

Cert has a lifetime and expires and you have to keep it up to date.

In Alberta for example the regulatory authority is APEGA: https://alis.alberta.ca/occinfo/certifications-in-alberta/engineer/

I think even technically the license is also a separate piece of paperwork.

Degree: you completed school at some point

Cert: up to date on current practices, must be maintained, requires the degree

License: you are legally allowed to practice in the province/country and have registered. Requires degree+cert

What if they are actually a software engineer, with a cert? >_>;

I have worked with actual cert'd engineers on web projects, lol

The two acts should be distinct for sure.

You should be also able to delete all history without deleting account.

Basically should be 2 distinct buttons/actions entirely.

Clinton cannot be tried again for the same crime under the Fifth Amendment.

Uhhh... shouldn't it be a mistrial now? Maybe they npw have to motion or whatever to get it classified as such before they can try him again.

Seems like the system is broken if they can't get it classified as a mistrial considering the dude literally got removed from the bench... >_>;

Here's hoping.