Oracle would like to know your location, but seriously they would so they can throw lawyers at you.

Really? TIL.

Missing type or identifier.

A const what?

Also, I read that you have to assign a const when it is declared. Something doesn’t feel right about this statement.

They do, but it’s a very simple speaker that’s really more of a buzzer than what you might think of as a speaker.

Many motherboards use a combination of beeps to report hardware errors if you fail on power on.

I’m impressed that the computer was usable with the failed CPU fan.

That’s good to hear! Very encouraging!

TP-link can’t open ports in the v6 firewall neither can Linksys and it doesn’t support DHCP forward so literally was incompatible with my ISP implementation. Some current TP Link router sold at Walmart don’t even have an IPv6 firewall.

Open source works great. Can’t speak to unifi never seen it for sale here.

You’re not an idiot. You’re using tools that don’t really do what they claim because it wasn’t considered an important use case.

IPv6 is great, but we haven’t seen enough pain yet to really drive adoption on the home LAN.

My solution uses the ISP box to deliver stateless auto conf, and bridging a consumer router. I can’t open ports but at least I get an IP.

I’m not using it because by and large it’s not implemented properly on consumer hardware, and my ISP doesn’t care if their IPv6 network is broken.

No you are right! Honestly it was several years ago and I struggled to remember exactly what I came up with before I left.

In our application we for example never use dynamic memory allocation. It has to be done very carefully so we don’t crash. Problem is there’s lots of sneaky ways one can accidentally do it from the standard library.

strtok is a worst offender that comes to mind. Global state. Pretty much just waiting to bite you in the ass and it did, multiple times.

Me too. If I can use it, I prefer C# — that is — if I’m not doing systems programming, I don’t have to worry about legacy code, and mainly I’m supporting Windows then it’s really quite cozy.

When I became a team leader at my last job, my first priority was making a list of parts of the language we must never use because of our high reliability requirement.

Underrated. It’s important to communicate that the parameters of the request cannot be satisfied as soon as possible. It might be a simple mistake from someone without a technical background who should instead be finding more resources first.

Therefore, would you agree that serverless is more about freeing up your mind as a developer and reducing your number of concerns where possible rather than necessarily cost savings or scaling?

In other words, is it less about better scaling and more about scaling isn’t your problem?

Thank you! I never knew about that site before.

Ever received a Slack or a teams message that’s just your name but no context as to what’s actually needed? Like they need to confirm you’re there but don’t want to reveal why they’re asking.

“John.”

Problem is whether or not I’m present has a lot to do with the question.

It’s even funnier when something like this happens to me and our IT guy goes I don’t remember installing that version…

Years ago I was told that serverless would be cheaper than running your own servers. It seems like it’s not necessarily cheaper, but just a different way of designing a solution. Would you agree with that assessment? I have never used serverless. Every place I’ve worked needed tightly controlled data so on premises only.

Meanwhile I host my personal website on dirt cheap VPS.

I now work for a small business but in the interest of not getting bitten in the ass I don’t wish to give the name of my previous employer. It was a large defense contractor, but our values didn’t align so I moved on when I found another opportunity to put food on the table. I know that’s not a satisfying answer but I’m here for entertainment value and the opportunity cost might not be worth it. My main point was that even though they have the money they didn’t see the value in good software process.

All the time! We would leave bugs unfixed even if the fix was trivially easy because management felt productive listing it as a cost savings. Software maintenance was seen as a necessary evil.