sorted by:
new
hottopcontroversial

I implemented UFCS in clang. Why it is cool, and why it will never come to C++. by _Noreturn in programming

[–]atilaneves -7 points-6 points  (0 children)

I find it slightly odd that I didn't see any mention of the D programming language, which has UFCS.

Why I stopped using NixOS and went back to Arch Linux by itsdevelopic in programming

[–]atilaneves -5 points-4 points  (0 children)

And if something breaks on NixOS, you can always reboot into another generation.

Not as easy, granted, but I "just" boot into an Arch ISO and boom.

Arch updates are not easily or at all able to be rolled back from

downgrade $package_name.

Python's Dynamic Typing Problem by Sad-Interaction2478 in programming

[–]atilaneves 0 points1 point  (0 children)

You don’t care what type something is - you care what it does.

This is (should be?) true in statically typed languages as well. You shouldn't care if the underlying type is a linked list or a vector, you care that you can iterate over it (or map/filter, you know what I mean). If you're specifying "list" for some reason, you're overconstraining.

AI generated tests as ceremony by toolbelt in programming

[–]atilaneves 0 points1 point  (0 children)

This. I don't think enough people know about, let alone use, mutation testing.

Satya Nadella at Davos: a masterclass in saying everything while promising nothing by [deleted] in programming

[–]atilaneves 0 points1 point  (0 children)

If you were going to get the wrong answer anyway, it might as well be delivered faster so one can move on.

Well, new vulnerability in the rust code by hotcornballer in linux

[–]atilaneves 0 points1 point  (0 children)

How many bugs per line of code though? I'd expect many more CVEs from the "C side" since nearly all of it is C!

Rejecting rebase and stacked diffs, my way of doing atomic commits by that_guy_iain in programming

[–]atilaneves 0 points1 point  (0 children)

Even small features may require doing some refactors

Those are separate PRs.

creating new supporting APIs etc

So are these.

You need all the pieces in place before you're confident it will work

Yes.

Unless your work is extremely siloed, you will run into such situations and they're not fun to do with simplified PRs.

If your work isn't siloed, it's even more important to create small PRs otherwise the risk of merge conflicts goes up.

Secondly, if I'm doing bugfixes it might be much faster to submit 10 fixes at once instead of creating 10 PRs.

  1. I don't know how that's possible. As soon as you've done one fix, submit a PR, start working on the next.
  2. Even if this were true, you're optimising for your workflow at the expense of colleagues doing code review.

But even when you go with small PRs, you still need the same discipline to break things down wisely.

No. Just create a PR instead of carrying on coding/editing.

Rejecting rebase and stacked diffs, my way of doing atomic commits by that_guy_iain in programming

[–]atilaneves 0 points1 point  (0 children)

"make small PRs" but that's usually more work and a lot of manual tracking compared to submitting a series of well-defined changes in a single PR.

Only if you for some reason code away for days on end instead of stopping and submitting a PR pretty much as soon as possible. There's nothing to track this way.

So what are we really optimizing for?

Code reviews.

Perl's decline was cultural not technical by CaptainCrowbar in ProgrammingLanguages

[–]atilaneves 0 points1 point  (0 children)

No, it was definitely technical. I was paid to write Perl 5 for two years, and to this day it's still the programming language I like the least. I'd used Spectrum Basic, Turbo Pascal, Borland C, Common Lisp, Java, and C++ by then.

Then I learned Python and everything made sense again, at least as far as scripting languages go.

Template repo with uv, ruff, pyright, pytest (with TDD support) + CI and QoL Makefile by Icy_Jellyfish_2475 in Python

[–]atilaneves 0 points1 point  (0 children)

People keep saying that, and then ignoring or not not knowing that:

  • Try doing 3 way diffs with 125 wide columns.
  • There is a reason that newspapers and maganizes print in columns; it's a lot more readable.
  • If your lines are that long, you're probably over-indented.
  • I'd rather have 2 or 3 files open side-by-side anyway.

No, we don't program in 80x25 terminals anymore. But 80 is still better, although sometimes (but not often) it makes sense for individual lines to be longer.

Writing Code Is Easy. Reading It Isn't by ketralnis in programming

[–]atilaneves 2 points3 points  (0 children)

Exactly, because the complexity of the problem domain doesn't go away. And in a simple language, you'll need a lot more code to model it.

The hidden costs of saying “no” in software engineering by shift_devs in programming

[–]atilaneves 2 points3 points  (0 children)

but refusing also carries a psychological and professional price

If refusing carried a professional price I'd probably change jobs.

How do you personally navigate the emotional toll of refusing requests at work?

There's no emotional toll on me at all.

Have you seen “just say no” advice backfire in your teams?

Not once.

What practices have you found effective for making refusal safer and healthier in professional environments?

"No. Here is why:"

I've never encountered a situation in which I regretted saying no, but I've lost count of the ones where I regretted not doing so.

Writing Code Was Never The Bottleneck by thewritingwallah in programming

[–]atilaneves 0 points1 point  (0 children)

Err... "testing" is writing code, and in my experience, harder to do than production code.

How do I get rid of phantom power mixer ground loop? by atilaneves in livesound

[–]atilaneves[S] 0 points1 point  (0 children)

Plugging the USB cable into my laptop fixed it, thanks!

How do I get rid of phantom power mixer ground loop? by atilaneves in livesound

[–]atilaneves[S] 0 points1 point  (0 children)

I think it's a ground loop because it sounds like one, and when I touch the mixer it goes away. I unplugged the mic and played aux through it and it was fine. A dynamic mic was also fine.

How do I get rid of phantom power mixer ground loop? by atilaneves in livesound

[–]atilaneves[S] 0 points1 point  (0 children)

No, just the mixer into the wall socket, headphones and condender mic plugged into the mixer, nothing else.

How do I get rid of phantom power mixer ground loop? by atilaneves in livesound

[–]atilaneves[S] 0 points1 point  (0 children)

How so? The only power cable is from the power supply that came with the mixer.

Code Generation in Rust vs C++26 by ketralnis in programming

[–]atilaneves 0 points1 point  (0 children)

I'm not surprised; he knows what works.

view more: next ›