nebeker

joined 2 years ago
[–] nebeker@programming.dev 2 points 6 days ago

I’ve seen some very excited sponsor spots for them on YouTube. CDNs often make ads load faster than videos, so who knows what kind of innovations they could be financing. All of them perfectly privacy preserving, of course…

[–] nebeker@programming.dev 23 points 1 week ago (2 children)

Thanks, I was confused about why the helix editor might need screen sharing. Haha.

[–] nebeker@programming.dev 2 points 1 month ago

Sure, it’s:

123 Mulberry '); DROP TABLE Deliveries;--

[–] nebeker@programming.dev 8 points 2 months ago (2 children)

I love how the documentation is in the actual .h file and the read me is a mere formality.

I’m disappointed I didn’t get this as a floppy in the mail.

[–] nebeker@programming.dev 1 points 2 months ago

Isn’t that the point of languages like Snap?

[–] nebeker@programming.dev 2 points 2 months ago (1 children)

A good reminder that composition is a useful concept.

[–] nebeker@programming.dev 2 points 3 months ago

I mean, if you want your prints to be asynchronous you’re looking for trouble to begin with.

The previous statement is a joke.

[–] nebeker@programming.dev 1 points 4 months ago

Ah, yes: weaponizing cybersecurity requirements to trick - I mean “motivate” - higher management to do things “right.”

[–] nebeker@programming.dev 8 points 4 months ago

My thought as well, but those stones were shaped to match each other, reducing the amount of grout needed. It just goes to show the old ways still work, but you have to commit.

[–] nebeker@programming.dev 16 points 4 months ago (3 children)

This is a dangerous metaphor. Remove the old wall and it turns out the new beautiful wall was leaning against and supported by it.

I get what you mean, it’s just that the metaphor could support both perspectives.

[–] nebeker@programming.dev 3 points 5 months ago

Surely through an intermediate - real - language?

[–] nebeker@programming.dev 5 points 5 months ago

I’ve said this before only to hear “we don’t have time to set that up and agree on a common style” and “that’s team B’s responsibility since we’re contributing to their code base.” Guess what kind of issue we kept wasting time on?

There are a couple of takeaways here. I think the main one is acknowledging that many technical problems are deeply human problems and the existence of a technical solution doesn’t mean we shouldn’t apply the human solution as well.

view more: next ›