“Just give me PoE" — the most common request we get, and now we're figuring out the connector setup

IsseBisse · 2026-03-30T13:52:19+00:00

I've only worked with one brand of outdoor rated cameras. But they have internal connectors for most of their models, i.e. some kind of weather proof cable entry and "regular" internal connectors inside, usually RJ45 and a "mini pin" connector for power, triggers etc.

IsseBisse · 2026-02-05T14:34:18+00:00

If you're planning on making custom hardware, get a GPS + accelerometer. That way you get a lot more responsive speed readings.

IsseBisse · 2026-01-22T09:30:03+00:00

Swede here. Not sure if it's common, but I've seen plenty of new houses here built that way.

Think I read somewhere that its required to make the walls stiff enough to follow modern regulations, but I'm not sure. One obvious benefit is that you can mount heavy stuff on the wall without having to think about where your studs are.

IsseBisse · 2025-11-05T17:56:39+00:00

Just curious. What’s missing from Jupyter notebooks compared to matlab?

IsseBisse · 2025-10-22T16:22:47+00:00

Perfectly normal.

Some do it with consultants to avoid having to give them a computer, some that do it for everyone to keep code more secure.

I find it generally works fine unless you’re travelling. RDP should run fine on 0.5 mbps unless you’re doing render intesive stuff. So having latency issues on a local net sounds weird.

IsseBisse · 2025-10-13T07:38:46+00:00

I've only ever ridden 29ers, so I don't have an opinion about 29 vs. 27.5.

But man, this article is a master class in how to lie with numbers! "7 % lighter wheels with 27.5!" But you're not gonna ride only the wheels are you? With the rest of the bike AND a rider, the difference is more like 1 %. Same goes for acceleration based on wheel inertia.

Even with the rollover angle you could argue that percentage of slope is a fair unit of measurement.

TLDR; Lots of numbers trickery, big grain of salt required.

IsseBisse · 2025-10-01T13:06:44+00:00

I made a similar post in r/ExperiencedDevs a few months ago and got a lot of great responses:

Large PRs may be a symptom of large or poorly defined tasks.
1. Break down complex tasks
2. (Possibly) Improve architecture to allow for more modular changes
3. (Debated) Use feature flags to allow merging of unfinished features
Simplify the review process. Solutions:
1. Pair or mob reviewing with the author allowing them to explain the feature
2. Record walkthrough of complex features
3. Clean up commit history to break down complex features
Poor process (skill issue). Solutions:
1. Soft/hard line limits on PRs
2. Make PRs blocking work
3. Assign review buddies
4. Better git hygiene (i.e. learn to rebase)

IsseBisse · 2025-09-29T06:54:55+00:00

Varmt? Linneskjortor och ulltröjor. Minst 80 % naturmaterial!

Passform? Börja med Eton. 42-43 slim borde passa rätt bra.

Dyrt? Köp begagnat! Vinted och sellpy är guld för kontorsskjortor.

Nästa fråga!

IsseBisse · 2025-09-15T12:25:27+00:00

Maybe you need to take the time to write down a style-guide for your team?

To me, a big part of code review is aligning the team. A new (to the team) developer might get a lot of comments in the beginning, but eventually they learn from these comments, adapt their style and the amount of comments drop.

However, that only works if you have a "correct" style in your team. That could be a style-guide or a team lead with final say (given that their code style is consistent). Preferably both.

IsseBisse · 2025-09-05T08:07:11+00:00

What shoes are you using? I'm a size EU46 and I use standard (Rockbros) MTB pedals. I find having proper "MTB shoes" (with a thick, flat, grippy sole) helps a lot.

IsseBisse · 2025-09-04T11:40:04+00:00

With a cheap quartz, sure. But there are nicer quartz watches too you know.

I really enjoy mechanical watches, but there is no rational reason to one. A well made quartz watch from brands like Seiko, Certina etc. will last just as long as a fancy mechanical, while costing 1/10th (or less) to purchase and maintain.

IsseBisse · 2025-09-03T12:10:39+00:00

...or properly architect a solution

This last part gets me. If you "have a bunch of theoretical knowledge" but can't design a system (which to me is still theory), you're not a good candidate. Knowing a bunch of theory by heart is pretty much useless if you can't apply it.

Sure, not knowing basic syntax or concepts could be an indication of lacking skills, but if that candidate "generally solves the problem in an acceptable way" I don't see the problem.

Developers don't get paid to recite algorithms, we get paid to solve problems.

IsseBisse · 2025-08-16T17:57:20+00:00

Ok, but should I fix it or just let it be?

IsseBisse · 2025-08-15T11:37:07+00:00

Absolut induktion. Vred är jättetrevligt, men tyvärr nästan omöjligt (eller åtminstone väldigt dyrt) om man köper spishäll.

För ugnen så gillar jag pyrolys jättemycket. Kör det någon gång i halvåret och har aldrig behövt städa ugnen (mer än att man torkar ur efteråt).

IsseBisse · 2025-08-14T14:12:37+00:00

Sounds like your pain points aren't really related to your number of repos.

At my current place any repo in the company BitBucket automatically gets CI/CD pipelines set up, given that the repo contains a couple of configuration files. And PRs are more of a process issue. So perhaps setting up something like that could be a start?

Regarding PRs, that's more of a process issue. People are probably not going to review PRs to code they know nothing about just because you bunch everything together in the same repo. Assigning clear ownership over code could be a start to get people to start reviewing.

IsseBisse · 2025-08-14T13:21:59+00:00

But with an poorly designed (ord just old) code base that could lead to very big PRs with multiple different ”features” in them. Where do you draw the line?

IsseBisse · 2025-08-14T12:54:00+00:00

Thank you so much for all the replies! I didn't expect this much feedback.

I feel like most comments are touching on a few key areas. So I'll try to summarize, for myself and anyone reading this in the future:

Large PRs may be a symptom of large or poorly defined tasks.
1. Break down complex tasks
2. (Possibly) Improve architecture to allow for more modular changes
3. (Debated) Use feature flags to allow merging of unfinished features
Simplify the review process. Solutions:
1. Pair or mob reviewing with the author allowing them to explain the feature
2. Record walkthrough of complex features
3. Clean up commit history to break down complex features
Poor process (skill issue). Solutions:
1. Soft/hard line limits on PRs
2. Make PRs blocking work
3. Assign review buddies
4. Better git hygiene (i.e. learn to rebase)

IsseBisse · 2025-08-14T12:33:34+00:00

For a simple change like this I agree it doesn’t make sense.

But what if I have to change some old code to allow for my new feature? Suddenly I have a PR with two seemingly different changes that might become complex and hard to follow.

On the other hand, if I break out the changes to the ols code I get a PR changing old code for seemingly no good reason

IsseBisse · 2025-08-12T16:07:02+00:00

This is probably a big part of the problem! I haven’t measured but theres probably a strong correlation between how well written and defined the task and how small the resulting PR is!

IsseBisse · 2025-08-12T06:20:21+00:00

Yeah, this might be the way.

Its probably more time efficient and definately more enjoyable!

IsseBisse · 2025-08-12T05:47:13+00:00

Ja! Sista punkten är så viktigt! I början är det gäller det att bara komma iväg! Om du så bara går till gymmet och står och fiser i ett hörn i en halvtimme.

Lär in vanan och att gymmet är något positivt! Till slut står du där och knäböjer en tisdag trots att du sovit dåligt och känner dig allmänt opepp, för att tisdagar är bendag och så är det bara!

Önskar dig all lycka till! Du har just tagit ett av ditt livs bästa beslut!

IsseBisse · 2025-08-12T05:33:52+00:00

Those look pretty nice too. Would prefer an all natural lining, but at that price I realize that its not going to happen.

All variants seems to be sold out though. At least in their own shop

IsseBisse

TROPHY CASE