HNHacker News
TopNewBestAskShowJobs

shandor

693 karma · joined June 3, 2016

submissionscomments
shandor··on Ask HN: What company environment has enabled your best work?
> Sure, probably this was more about him being a good manager than the "process" behind it.

Of course also that, but you're completely right that that is the exact job of the Scrum Master. To "remove impediments". No matter if the impediment is some process or a manager, it's the Scrum Master's job to remove it.

This actually aligns pretty well with the ideas in Agile Manifesto. And that's why I'm so sad when "scrum master" nowadays mostly seems to mean someone who counts the minutes devs spend on each Jira ticket, and haunt the team when velocity seems to be dropping 10% for the second day in a row.

shandor··on Imperfect Forward Secrecy: How Diffie-Hellman Fails in Practice
Is libsodium the de facto standard instead of the original NaCl?

If so, what are the reasons? Just enhanced usability, since I recall libsodium using the NaCl crypto primitives almost directly as-is?

shandor··on Google AMP case study: leads dropped by 59%
I remember this being speculated heavily as one of the most important reasons for Google implementing AMP in the first place.
shandor··on The Waterfall methodology was a historic accident and they knew it
I agree with your conclusion fully. Also your link to "eat well and do sports" is kind of exactly what I was after. I mean no one is saying that eating well is bad for your health, right? What I was trying to convey is that I think similarly of the Agile Manifesto itself.

Because we shouldn't infer that eating well is bad because a lot of people try to eat well and are still obese, we shouldn't infer that Agile as in the Manifesto is bad because lots of companies get burned by Scrum. We should be coming to conclusions like "hey, maybe this Scrum thing we tried is shit, let's try some other process that seems to align with these fuzzy agile values we believe in".

The problem I have with the current discourse around the matter is that as long as we keep bashing "The Agile Values" when we mean "agile processes as implemented in framework ZZZ", we are not having the discussion of "hey, which process would align better with these values while letting us ship quality software rapidly".

shandor··on The Waterfall methodology was a historic accident and they knew it
> I've come to the conclusion that Agile development processes do not represent a real-world solution.

I think one of the problems regarding this whole discussion, whenever it stirs up, is that Agile (as defined in the original manifesto) is explicitly not about any particular processes, but still most of the critique against Agile seems to actually be against different kinds of "agile processes". The manifesto explicitly states "Individuals and interactions over processes and tools".

In real world, one of course needs actual processes, and all kinds of consults are trying to ride the wave to lucrative contracts. But since the Agile Manifesto is about values, not processes, you cannot steal it from its creators. You can pervert the meaning and utilize some braindead processes in your company and call them "agile", but that doesn't lessen the worth of the original values.

I know that that's a highly unsatisfactory answer, a kind of a cop-out, but I think applying more to Agile than it's meant to be is part of the problems surrounding it today.

Edit: those "you"s are meant for passive voice. No personal offense or commentary meant.

shandor··on JIRA is an antipattern
Any concrete examples you could share? This sounds like an absolutely fascinating take on the matter.
shandor··on Slow Software
p4merge is indeed awesome. I work exclusively in Linux environments, but p4merge always gets installed. The experience has actually gotten better in that regard since git started supporting it straight as one of its 'mergetools'.
shandor··on Cloud Computing Without Containers
What are some container technologies that could be used for this right now?
shandor··on Ask HN: How is Facebook's iOS app 491MB?
And also move to mbasic.facebook.com for even more blazing fastness!
shandor··on Changing Our Approach to Anti-Tracking
What about Tizen? Haven't been following it too closely, but isn't it a kind of descendant of the Meego platform in some sense?
shandor··on Apple to Close iPhone Security Hole That Police Use to Crack Devices
Doesn't matter, both of them are offered by the OS installer and are easy to set up.
shandor··on GitLab Ultimate and Gold now free for education and open source
We've been pretty happy with Phabricator. Its code review is miles ahead of the others, in my opinion, and other parts also work well for us.

Of course, it's not a direct replacement, since they don't have free, centralized service like GitHub/Lab does. But, it's 100% open source and you can easily host it on a potato.

shandor··on Inside the Linux boot process (2006)
Because a hibernated machine is still powered on. So you're correct in a way, the "boot process" from hibernation does skip a lot of things.

Problem is, you can't utilize those shortcuts when doing a completely cold boot. Like another commenter said, in that case most of the boot time is preparing hardware.

shandor··on Google loses ‘right to be forgotten’ case
When EU dictates what can be in the search index it is "right to be forgotten".

When China or Russia does it, it's at least "censorship", and probably also "dictatorship".

shandor··on Does wearing glasses weaken your eyesight? (2014)
Interesting. Do you have links to any studies I could read on the matter?
shandor··on Mozilla announces an open gateway for the internet of things
> MQTT is an insecure hack.

How so? Usually when I hear someone talking about MQTT, it sounds like it has to be the best thing since sliced bread.

shandor··on Best practices for user account, authorization and password management
Where did you get that "messages and posts" are included in data that falls under the regulation? Not contesting, genuinely interested. I was under the impression it only covered personal data in a very strict sense (names, addresses, personal info like gender, etc)
shandor··on The Rise of German Board Games
The solution is to only play Diplomacy with a group where everyone is a known scheming backstabber who will never trust one another ever again for the rest of their lives! Have tried, can confirm it works. Good times.
shandor··on OpenSSL wins the Levchin prize
> It great that OpenSSL have improved quality, yet it feels like they're rewarded for cleaning up their own mess.

Though to be honest, an insane amount of stuff relies on OpenSSH for their security, and has for years. If their code was messy earlier, ok, but they have still been basically de facto standard SSH client for much of networking. I'd say their prize is well earned.

shandor··on Things I have learnt as the software engineering lead of a multinational
> there's rarely a discernible difference in revenue between a high quality release and a buggy, low quality release, but the profit margin of the former can be (and often is) much lower.

A wonderful insight, thanks.

I guess that hints in a direction where "both are Right". For the technical teams, it's self-explanatory that "one does not simply push out crap". On the other hand, the MBAs and finance hear engineering say the same thing about mostly everything, and double profit margin is double profit margin, so the incentive structures that encourage faster releases probably seem completely plausible to them.

Not that things are that clear and clean in real life. But having drifted from pure engineering to engineering management during the years, I feel more and more sympathy towards some of the challenges of the "ugly and evil business side" by the year. Also, nothing is as hard as communication. Except trying to communicate goals with broad incentive structures, I guess.

shandor··on Many major websites are taking silent anti-ad-blocking measures
Firefox for Android is wonderful after Quantum. uBlock Origin works fine with it, and you can even use the custom filters to purge the scourge of the so called "dickbars" from your browsing experience. It's not as streamlined to use as with a mouse, but never having to see those Medium banners again makes my Internet life so much better.
shandor··on Why don’t software development methodologies work? (2014)
I feel like this actually explains a surprising amount of things that look silly at face value.

Another example I've talked a lot with my colleagues is company wide coding style definitions. They usually have stuff like "never ever use goto", but then you have Linux kernel code using goto, and it seems all weird. But here too the coding convention that feels "stupid" to the rockstar coder is in place to make the code of the summer intern even remotely usable after they are gone.

shandor··on My 20-Year Experience of Software Development Methodologies
That's the first time I hear about Kepner-Tregoe. Would you have any pointers to some basic reading on its principles?
shandor··on Linus Torvalds: “Do No Harm”
I think the most important point here is that with those different patch sets, the more security-conscious users/companies get to have the properly hardened version immediately into use, rather than running the "only report" versions for what might be years, as you say.

Granted, I'm looking at this from a perspective where our company compiles our own kernel for use in embedded devices, so we can have whatever patch sets supported we want. But I think that's much better than everyone having to use the "report only" patches for years, or even worse, the features never getting into the kernel in the first place.

shandor··on G.E.R.T: Golang Embedded Run-Time
Impossible to answer in general context :)

Nowadays anything from 16kB to 2GB of RAM gets called "embedded". Storage is the same but x10.

I would be surprised if there's nothing to use Go for in all that design space, but generalizations are probably plain impossible.

shandor··on A successful Git branching model (2010)
It would be optimal if the team can have the discipline to never commit broken stuff, and we could live with "everything in master must be working all the time".

If that does not work in reality, or breaking it would simply cost too much (because mistakes will happen), I'd use release branch or use git tag to mark versions with "no really, this one really truly actually works in every way".

For your second point, see 'git revert'! It does exactly that, i.e. picks a commit and effectively removes it from a branch by making its "mirror commit". The other way is, of course, just deploying an actual fix asap, git revert is just for when fixing the problem is for some reason or other slow and master must be unbroken immediately.

shandor··on A successful Git branching model (2010)
My bad, I was going to edit my comment to be less coy and more constructive, but I'll just continue here.

Even though I always advocate rebasing, I also think that WIP commits should not reach master as-is. We are actually using Phabricator with my current team, and they have a really nice opinionated way of doing development. All dev happens usually in (really short-lived) task branches, but once they have gone through review etc. they are landed on master as one single commit, with the commit message holding all the relevant information about the change(s) made in the original task branch.

The reason for not having the WIP commits on master is that "commit early, commit often" is good practice, so the sheer amount of WIP commits will completely drown out the actual, finalised changes (i.e. the "actually interesting history as in a history book") in master. So no, I don't think squashing is a bad idea, I think is absolutely essential if you rebase onto master. If you don't squash, rebasing might lead to more mess than using merge.

Now, as to keeping WIP commits. I think that their value is usually much overestimated. I can count the times I have needed to go back to the actual, raw WIP commits instead of the properly rewritten one in master with one hand. But if you feel that it's the only thing keeping you from switching from merge-intensive flow to a always-interactive-rebase one, I'd encourage you just to retain the original, short-lived development branches in origin as separate branches. IMHO that gives best of the both worlds, if you think throwing out the WIP commits could hurt too much.

---

Edit: oh, and having massive squashed commits should not usually be a problem because mostly they should not happen. Individual tasks should be so small that implementing them can not result in a massive amount of changed lines.

shandor··on A successful Git branching model (2010)
I always advocate workflows where merges never happen.

To me, the 'git log' of a master branch is like a history book about the repository. When you read through it, it should give you answers to the questions "what was changed, why, and when" in as clear format as possible.

Now, I've read most of the arguments trying to show that merges are the way to do just this, instead of rewriting history with interactive rebasing. I won't repeat them all here, but just want to ask this: when one reads a real book about real world history, does it look more like git log history of a repo which has been using rebase, or merge?

shandor··on Modern terminal-based text editor
Sure, my meaning wasn't to talk down the project itself, it looks neat! The "MB does not matter" just jumped at me (somewhat out of context, I have to admit) since I work in the embedded land, and the pain is sometimes too real there.
shandor··on Modern terminal-based text editor
> Because MB don't matter

I beg your pardon, but since Linux is increasingly used nowadays in quite resource constrained embedded devices, MB definitely does matter. (No, I don't claim that the individual 10 MB is very much on most devices that are actually capable of running linux. But once you go down that road and start having something else bloated than just the text editor, you are a few hundred MBs poorer in no time, and that is a lot.)

← PreviousPage 5 of 7Next →