dakiol (u/dakiol) - Readit News

dakiol commented on Things I want to say to my boss ithoughtaboutthatalot.com... · Posted by u/casca

arevno · 6 days ago

That's because many of us older developers got into the profession when it didn't pay well, and had negative status associated with it, because we loved doing it.

So yes, there is very little tolerance from us toward those who are in it for money/status/prestige, and not for the love of it.

dakiol · 6 days ago

I feel divided. I do love my career (computer science/engineering) and I dedicate a lot of my free time to it (reading tech books, doing side projects, HN, etc.). But at the same time, I don't give a damn about my company. I hate the leaders, C-level execs, ... I cannot stand them, and it's not just my company, it's almost every tech company out there; so I work for the money, and take pride of my skills when working on open source and the like.

dakiol commented on Ego, empathy, and humility at work matthogg.fyi/a-unified-th... · Posted by u/mrmatthogg

dakiol · 23 days ago

I think the article mixes different things.

> That’s the way we’ve always done it.

That's not ego, that's laziness. At least based on experience, engineers are reluctant to change simply because they feel comfortable enough with their codebases.

> Assign it to me. Nobody else will be able to fix it.

Yep, that looks like ego.

> This feature is too important to assign to the junior dev.

Bad communication style perhaps? There are features that require a senior to drive them. What's wrong with that? Sure thing, I wouldn't phrase it as the author, but I don't see the ego anywhere. I see transparency and being upfront.

> We should start using this new tool in our pipeline

Again, perhaps it's just bad communication style. An engineer that says this is someone who cares enough to suggest things, even when nobody is asking. I know engineers who never suggest (or gatekeep) anything, they simply don't care

dakiol commented on Ask HN: What tools do you pay for today that feel overpriced or frustrating? · Posted by u/psicombinator

dakiol · 23 days ago

LLMs subscriptions. Ideally I wouldn't need to pay for top-notch software (e.g., linux, ffmpeg, qemu, etc.), but here we are.

dakiol commented on Ego, empathy, and humility at work matthogg.fyi/a-unified-th... · Posted by u/mrmatthogg

drdaeman · 24 days ago

> The following is a short, incomplete list of typical statements we as developers might say or hear at work. If you parse them more precisely each one is an attempt at self-justification: […]

> “We should start using this new tool in our pipeline.”

> “We should never use that new tool in our pipeline.”

I don’t get what’s “wrong” with those two. There’s no justification (self- or otherwise) whatsoever in any of those statements, not even a hint of an attempt. Justification, as I understand it, requires a “why” (possibly, only suggestively implied, but nonetheless present in some form) and I see absolutely none, just a call to action.

If someone sees it, can you please explain?

dakiol · 23 days ago

Agree. I rather work with people who suggest stuff ("We should start using this new tool in our pipeline") than with people who ever suggest anything (typically they don't care).

dakiol commented on The fate of "small" open source nolanlawson.com/2025/11/1... · Posted by u/todsacerdoti

cynicalsecurity · a month ago

He almost got it right. It's not just the fate of small open source. It's the fate of all programmers now. Why hire a programmer when an LLM costs less, works faster and makes less mistakes (OP compliments better error handling, read the article).

Unless you are a product owner, you have paying clients that love you and your product and won't simply ditch it in favour of a new clone, you are really screwed.

dakiol · a month ago

So far I've never seen yet a non-programmer release production-grade code using only LLMs. There's just so much to care about (from security, deployments, secret management, event-driven architectures, and a large etc.) that "just" providing a prompt to create an "app" doesn't cut it. You need infra and non-engineers just don't know shit about infra (even if it's 99% managed), you need to deploy your llm-generated code in that infra; that should happen in a ci/cd probably. And what about migrations? Git? Who's setting up the api gateway? I don't mean to say that LLMs don't know how to do that, but you need to instruct them to do so, and even there, they will make silly mistakes and you need to re-instruct them or fix it.

Prompting is just 50% of the work (and the easy part actually). Ask the Head of Product or whoever is there to deploy something valuable to production and maintain it for 6 months while not losing money. It's just not going to happen, not even with truly AGI.

dakiol commented on Ask HN: Typical tech job interview in late 2025? · Posted by u/dakiol

luponius · a month ago

Had interviews last year insisting the use of llms and others tolerating it. Our head wants to introduce codex in ohr workflows now so pretending you're not using them or joining a team that swears off them better have a very good reason I suppose?

dakiol · a month ago

Yeah exactly. I'm using codex, btw. So I feel weird to pretend I'm not using LLMs and I write all code just by using my brain. But on the other side, there's no much point on explaining one-self on how LLMs are used to do a task... like, it would look very ridiculous to share my screen and ask 90% of the solution to the LLM while the interviewer just looks at LLM output... that's like analyzing how one uses Google to search for stuff (and I swear that 100% of the engineers out there use Google to search for stuff related to coding, but I haven't heard of any tech interview that includes a session to asses your Google skills, right?)

So, if we are not pretending, and companies want people who can use LLMs, well, I think it's rather clear: No more live coding interviews, no more live system design interviews. You can just send take-home assignments because people WILL use LLMs to solve them. You just analyze the best solution offline and take the best.

If any the only "live" interview needed is: are-you-a-real-person-and-not-an-asshole?

dakiol commented on Jujutsu at Google [video] youtube.com/watch?v=v9Ob5... · Posted by u/Lanedo

dakiol · 2 months ago

I've worked in huge repos with hundreds of developers pushing code every day, dozens of MRs open per day, and all I always needed was a very limited set of what git is capable of (git commit, git co, git st, git merge/rebase, git log).

To find bugs, I use "bisect but visually" (I usually use jetbrains IDEs, so I just go to the git history, and do binary search in the commits, displaying all the files that were affected, and jumping easily to such versions).

Git conflicts are easily solvable as well with a gui (jetbrain IDEs) via the cli or via something like Sourcetree. Easily, the most used "feature" of git that i use is:

- for a given line of code, see all the files that were touched when that line was introduced

But I usually do that via the IDE (because to go through dozens of files via cli is a bit of a hassle for me)

So, what am I missing? I know jujutsu is much simple (and powerful) than git, but I only have used the "good parts" of git and it has never been a bottleneck... but ofc, you don't know what you don't know.

dakiol commented on Mistakes I see engineers making in their code reviews seangoedecke.com/good-cod... · Posted by u/zdw

dakiol · 2 months ago

It's not that complicated:

- you review and if to the best of your knowledge you think something can be done better you comment about it and leave a suggestion on how to do it better

- then you approve the PR. Because your job is not to gatekeep the code

dakiol commented on Mistakes I see engineers making in their code reviews seangoedecke.com/good-cod... · Posted by u/zdw

rkomorn · 2 months ago

The way I look at it, commenting without approval means "I don't approve (and here's why) but someone else can."

Blocking means "I don't approve and no one else should either."

dakiol · 2 months ago

> I don't approve (and here's why) but someone else can

That just sucks... because with that mindset typically nobody approves and leaves the submitter begging for approvals.