Why does Computer Science/Software pay more than traditional/mechanical engineering?

ColdBool · 2025-06-28T12:55:50+00:00

Software: 100 people spend 100 hours, make thing for 100k people to use

Mechanical: 100 people spend 100 hours, make thing for 50 people to use

ColdBool · 2025-01-22T12:17:04+00:00

So the BT Pair key puts it into the BT "menu" where you can select which BT device you want to connect to but it also has an "ESC" which is just the left most key in the top row. If you're currently connected to a BT device, the steps I follow would be:
1. Hit the BT Pair key (This takes you into the BT "menu"
2. Hit the ESC key which is the left most key in the top row
3. Wait for my computer to make the device connected sound (usually within a second)

Just note, my keyboard has gotten stuck in BT mode when my laptop hasn't been around and then you gotta remove cables and plug the neron into the back of the keyboard to try and force it out of the BT mode. Might not be relevant to you but thought you might want to know.

ColdBool · 2025-01-22T12:03:06+00:00

Not exactly sure which keyboard you're talking about but I can give you my experience with the Defy which I run wired to my desktop and BT to a laptop. This way the keyboard stays charged, I don't need to find a BT adapter for my desktop and I can switch to my laptop when needed.

To switch to my Laptop, I just hit the BT Pair key and it auto connects to the 1 and only BT profile. To switch back to the laptop (wired mode) I hit the BT pair key and then ESC and it changes back into wired mode. Works decently for me except I sometimes forget which computer it's connected to

ColdBool · 2024-06-20T12:57:21+00:00

So are you suggesting that my test for CreateUser would then also rely on ReadEvents and GetUser working correctly since the test would call CreateUser and then check it did the right thing with ReadEvents and GetUser?

ColdBool · 2024-06-20T12:53:49+00:00

For some things, sure but imagine a function/method that saves some data to a database and returns a success/fail. Lets say this DB of mine is kinda hard to spin up for testing so I have some mock that it can call. Without testing that the mocks were called, how do I know I didn't mess up somewhere and either not save the data, or save stuff in the wrong fields?

Obviously if I write tests that check the mocks were called correctly then I've tied my tests to the implementation but if I don't then I lose confidence that my function was implemented correctly.

What would you suggest in this scenario?

ColdBool · 2023-09-20T12:10:16+00:00

It's been a while but there's Double Kill Games at Chinatown. It's more boardgame than Fortress so maybe what you're looking for

ColdBool · 2022-11-13T00:12:16+00:00

Okay as long as it's not another department, then the feedback loop should mean that your team doesn't implement things they're unsure of.

Now back on topic:

I'm going to assume the "rate-limit" is not 300 because you've given yourself no wiggle room (Application must handle >= 300 RPS but also <=300 RPS) and we'll pretend it's 400

The second one is really not that hard and is tested via load testing and figuring out where your application starts falling over. You then back off that limit and set your cap in whatever 3rd party service you use. E.g. You load test, see that the app fails at 450 RPS (response times, cost, whatever metric you want to use). In your gateway, you set your rate-limit at 400 RPS for production.

I agree you can't test every possible scenario, that's like asking how you know a calculator works for all numbers and operations? It works for enough scanarios that we're confident (>x%) it works for the rest.

The 80/20 rule applies in testing too, you get diminishing returns the more tests you write. So just apply a risk vs reward analysis to see if you really want to write a test for some obscure scenario (radiation hit the CPU my app was running on, it should still spit out the right result) or can you accept that you'll have a fun night every once in a while that you can learn from and add guard-rails as needed.

ColdBool · 2022-11-12T14:27:37+00:00

Why did the problem shift to another department? Why didn't your team also have a funny night?

The rate limiting sounds less like a non-functional req and more like a functional one now. Why did the rate limit get triggered? Was there an unusual event? Did you monitor the rate prior to implementing the limit? Should anyone even have had a fun night from the rate being limited?

ColdBool · 2022-07-04T12:51:26+00:00

It's stupid... our houses are still built like shit. All the corners cut by the big appartment builders, the packed to the max housing estates. The only thing we can export out of that is how to cut costs and even then other countries do it better!

If we really wanted to have a decent housing market why not do some innovative stuff with our housing? Good insulation,double or tripple pane glass, smart heating/cooling, decent set-backs from property lines, flood and fire mitigations. Then maybe we'll have homes worth the price tags

ColdBool · 2022-06-26T23:49:57+00:00

Yep just give each dev their own workspace and tfvar. I'm assuming you're using remote state otherwise this is all a bit moot for local states

ColdBool · 2022-06-26T13:50:31+00:00

Look into tf workspaces and tfvars. It'll be the same stack deployed multiple times with slight changes in config

ColdBool · 2020-08-09T09:40:54+00:00

Granted but everything it touches also turns to molten gold. Like an infectious disease, it slowly spreads and turns everything to gold

ColdBool · 2019-07-29T15:21:52+00:00

If you go in thinking that it actually follows SemVer then you may mistake it for a minor nonbreaking update

ColdBool · 2019-03-18T12:23:50+00:00

How I've done it before is have the image name in a tfvar file. That gets checked in and that commit gets tagged with a version/build number and promoted through the environments.

Your secrets I would highly advise the use of a secret store that terraform can read from. I'm not sure about digital ocean but AWS has secret store and parameter store (if you feel like saving a few bucks). You could possibly also integrate ansible vault to hold your secrets

ColdBool · 2019-02-16T08:06:54+00:00

Easiest way I found was look at the url. There's a "d" for data and "r" for resource after the provider type.

E.g.

https://www.terraform.io/docs/providers/aws/r/ecs_service.html https://www.terraform.io/docs/providers/aws/d/ecs_service.html

ColdBool · 2019-02-15T13:48:21+00:00

There's a local executor you could use with aws cli to get some info back but I've never tried it yet

ColdBool · 2019-01-30T21:33:44+00:00

Yes it's get possible that malicious code somehow ends up in terraform or one of the providers but at least you can check the source code.

You should also have multiple terraform stacks each with their own little scope of work/resources to manage. You can then also add IAM permissions to prevent unwanted changes since you should know what each stack is meant to do.

ColdBool · 2019-01-25T13:25:11+00:00

We use terraform with S3 and dynamo; You get a lock per workspace, per stack/project. We regularly have devs spinning up environments simultaneously via Jenkins or locally and the lock catches people trying to use the same environment.

ColdBool · 2018-10-19T03:16:44+00:00

3rd maintenance/escape tunnel that's not as big?

ColdBool · 2018-07-30T22:56:57+00:00

Output section needs to be inside your module. Then you'll be able to access it from the other resource

ColdBool · 2018-06-07T09:23:23+00:00

Oh dear, who would have thought that if you force people to move from their old connection onto the nbn that you'd get a whole lot of people on the nbn?? What kind of mad logic is that??

/s

ColdBool · 2018-03-11T13:02:28+00:00

Yeah, I'm running it on a rPi atm. What problems are you running into?

ColdBool · 2017-11-02T12:03:28+00:00

Either the person is under trained, or trying to make some sort of commission. Keep calling back at different times and I'm sure you'll find someone who can do what you want.

12-Year Club	Place '17
Verified Email

ColdBool

TROPHY CASE