beaker

joined 1 year ago
[–] beaker 5 points 1 year ago

I understood perfectly and I bet a lot of others did too. I bet you understood it. So, mostly or completely successful use of the word to inject the desired thoughts into others' heads. So, the word works that way, even if it sounds awkward to you.

[–] beaker 35 points 1 year ago* (last edited 1 year ago) (2 children)

We made the decision yesterday to dump Postman in favor of Thunder Client. As soon as I saw the push to create an account and use cloud workspaces, I knew the time would come.

(edit: correct styling of Thunder Client)

[–] beaker 7 points 1 year ago (4 children)

I'm on my second Dell XPS 13 Developer laptop which comes with Ubuntu pre installed. I loved the first one but played too much Minecraft and wore out a couple of keys. I had it long enough that decent replacement keyboards were hard to find so I got a new laptop from the same line. I love the second one even more. My brother, also a Linux-using software professional, made the initial recommendation, so there is at least one other person who liked this line.

[–] beaker 2 points 1 year ago

I assumed this was the case and that any reporting on "users" and the "historical" nature of their short time to 10M users was 100% BS.

I think the strategy is great and I would do the same that they are doing, except I'd leave out the bit where I crowed about reaching 10M users in 7 hour or 100M in a few days. It's too obviously a lie supported by the ability to leverage one network into another.

[–] beaker 2 points 1 year ago

Ceramic knives, fish spatula, and the immersion blender.

[–] beaker 8 points 1 year ago

That's terrible! Didn't we all learn that each method must have exactly one return statement? Please refactor to use a return variable and a single return. And get off my lawn!

 
[–] beaker 2 points 1 year ago

Gaining weight or losing weight?

What problems do you have? Are you having latency issues that could be resolved by reducing external dependencies? Are you having difficulty synchronizing multiple components that each implement the same behavior?

It's better, in my view, to know how to tell what challenge your code is actually facing. Sometimes this will lead to more aggressive decoupling and sometimes it will lead to externalization of shared functionality. Deciding these things ahead of time is a recipe for fanaticism.