HNHacker News
TopNewBestAskShowJobs

mmatants

447 karma · joined May 21, 2011

Nick M
submissionscomments
mmatants··on Thought Experiment: GitHub Community View
Agreeing with the premises, let's call this what it is - a recommendation/curation problem, which a kind of thing that a trusted third-party usually does. Seems like it would fit as a Community Explorer blog/engine, as a separate presence.

Except we already have powerful personalities in the development space who already share their opinions and value systems - this is a natural extension of that. After all, a lot of choice of what is the "right" fork or even the "right" tool to begin with gets back to subjective developer experience and intuitive tech preferences. And that's something that a platform like GitHub should stay neutral to.

mmatants··on Write code that is easy to delete, not easy to extend
Funny you mention monolithic code. The post expressed a very important thought:

> we’re trying keep the parts that change frequently, away from the parts that are relatively static

Modularization and good code contracts help "sequester" code parts with different rates of change.

And this is my guiding hunch when I am splitting up code and deciding on module surfaces: how confident are we in the subject matter that given code describes? This does not replace actual proper concept modeling, but it is an intuitive feel for helping future iterations go smoothly.

mmatants··on Why Shitty Products Survive and Thrive
Feels like for institutional tools (where end users are mandated to just use that one system) it's not even the retention that is the problem.

I would generalize it (perhaps ad absurdum) instead as: do not underestimate costs of user onboarding (in whichever shape or form).

I wonder if developing a competitive replacement app actually involves replicating legacy UI. As wasteful as that may seem. And only after that hurdle is nullified, there will be a chance to gradually wean users towards a new experience pattern.

mmatants··on BarleyDB: An alternative approach to Java ORM
Glad to see folks critique traditional ORM tropes and putting forward some innovation in the area.

On that note, as a highly subjective opinion, I have really soured on the philosophy that guides many popular ORMs.

Relational data does not map to OOP well, and I think the point is not to actually force that. Instead, I think there are ways to embrace the relational model, because it is actually quite apt for many business cases.

For those further interested in the general topic of alternate ORM approaches, here is a link to a proof of concept from a while back, when I was exploring how to express column-driven data in Java code: https://github.com/fxrm/fxrm-store-java

This is not to hijack attention from the OP idea, of course; just noting that this is still a fruitful area of improvement in software.

mmatants··on Jack Dorsey addresses Twitter's character limit
The reason to mention image posting is specifically to say that they want the UX to be like a text attachment rather than just a wall of text on someone's feed. Which is a much smaller disruption to existing experience.

On that note, the fact that images are being used to show text content on Twitter right now is laughingly unfair to folks who use a screen reader, given how much we value HTML for its presentation flexibility.

mmatants··on The Same User Interface Mistakes Over and Over
If you decide to study how to build bridges, you will start out with calculus, build a background in science of materials and then a guided tour of approaches to structure-building. In addition, you have to learn typical environmental factors. And, of course, there are workflow patterns and human factors involved in actually constructing a typical bridge. Oh, and sure, there will be a bit of CAD.

Let's apply this metaphor to programmers working on UIs: a huge chunk of practitioners right now get by via simply having learned a bit of CAD (i.e. HTML/CSS/JS). And also, yeah, they have walked over a bridge once/seen a panoramic postcard, so there's that. Very ad-hoc, very disorganized, full of gaps.

Of course the impact of mistakes is magnitudes different between designing bridges and building UIs. Except for when that UI drives medical automation. Or finance (one of my faves is an anecdote about how a bad input form field cost a fund management company literally in the 8 digits of money).

Our industry is of course very young, and so I think this education gap is simply a temporary issue. I am looking forward to (and am personally investing into) a day when there will be a more systematic and comprehensive education on how what a good UI looks, behaves and feels like, not just how to code buttons and boxes on a screen.

mmatants··on Twitter’s updated Mac app wasn’t made by Twitter
At least in theory, agencies also do a lot of account management legwork. Of which there is a lot for large clients. Which merits critical attention, but there it is for now.
mmatants··on How Completely Messed Up Practices Become Normal
I recall reading somewhere that while military organizations are very much synonymous with hierarchy, they have historically experienced a lot of pressure to flatten and decentralize, at least as far as field command goes. Napoleon's success was attributed to smaller units that responded to feedback more quickly. Unfortunately I can't find that article.

However, this is not to say that in regular administration there isn't still a lot of de facto trust in the hierarchy. I think unbounded hierarchy is generally one of those memes that people grow up taking for granted as something that just works with any layer count. In some ways, it's a self-reinforcing thing - if you climbed ranks for 10 years, you don't want to see the system change and your "sunk cost" go away.

[edit: clarified sentence]

mmatants··on How Completely Messed Up Practices Become Normal
The other tl;dr is that managers need to know and buy into concepts of group psychology.
mmatants··on Will the true component please stand up
I would like to examine the concept of properties as it exists in modern OOP with a more critical eye.

If a property is independent of other properties, then that means it is an independent holder of state. So then, wouldn't it be a prime target to be split out into a composable sub-component?

It just feels like many classic examples of components have been over-stuffed with properties. Kind of goes against the perspective of objects as minimal black boxes. Composability might go a long way to clarify that.

mmatants··on The Canadian who wants to dethrone Facebook
For that matter, most social contexts involve signalling adherence/allegiance to a specific set of values and beliefs: clothing is almost always a uniform of sorts. It helps establish an initial foundation for further communication.
mmatants··on Facebook '2G Tuesdays' to better understand markets like India
This is why I am perfectly happy with our team's local Vagrant development boxes being quite sluggish - the visible lag has surfaced a few timing and UX bugs already. It's important to feel the customer pain as your own.
mmatants··on Clef's company handbook
That's definitely a danger, and it's not an either-or thing, of course, as well.

I think the point of that advice is to remind that for an astounding amount of people empathy is not at all a priority! It may be even seen as a weakness, in an unspoken way. Humanity and empathy should be a core value on a company's banner precisely because it's fairly explicitly discouraged by default in personal and work culture at large.

mmatants··on Why Fogbugz lost to Jira
Here's the issue, though - no matter how violently we may agree on the downsides of traditional project management, opinionated tools are just ahead of their time. The market is not at all ready to agree on what software workflow should look like. It just takes time for good techniques to propagate - this is such a young industry...

So until there is stable consensus among everyone up to even late adopters about how software work should be managed, any opinion built into the tool will end up being an obstacle for users who are still yet to learn agility the hard way.

The real value of an opinionated tool is the opinion itself. And that is something that has to be instilled first. Build a knowledge-base, a following, a community, then make the tool a companion piece.

mmatants··on Microsoft Edge gets native ECMAScript 7 async/await support in latest build
In some way, promoting the use of "await" actually reduces the chance of an exception floating away into the ether. The "thread" joins back, both on success and on failure. And because promise errors are like exceptions, it's probably not a great idea to signal commonly-occurring conditions through them (instead using sentinel values like nulls, etc); so there isn't a huge pressure to try-catch every single thing.

Also, there is fundamentally nothing wrong with a promise error that never gets handled. It's an "if a tree falls in the woods" kind of thing, no? I will concur that it's not exactly beginner-friendly, though.

mmatants··on An Introduction to Taxicab Geometry
I've seen this distance measurement mode referred to as Manhattan distance (https://en.wiktionary.org/wiki/Manhattan_distance), but it's interesting to see the full theory around it (and of course taxi-cab geometry is the more properly accepted name).
mmatants··on On doing things other people can't
In fact, the secret of the not-as-young people is to manufacture the luck as much as they can and increase exposure to serendipity through consistent - well - showing up. And behind most lucky youngsters are diligent parents and support networks that know this lesson and apply it to their offspring, even if the offspring stay unaware.
mmatants··on Literary Magazines for Socialists Funded by the CIA, Ranked
Every political ideology claims to make things better (if only for some folks). The practical question is - which one is likely to devolve into a pathological state, given a historical and cultural milieu where it is implemented, plus the natural limitations on information transfer between humans and entropy that pushes against our organizational efforts?
mmatants··on Multiple Vulnerabilities in Pocket
It's hard to get an intuitive feel for security.

If team principals are mostly young and don't have exposure to very specific kind of experiences dealing with threat modelling, then the security work will always take a backseat to feature-building. It's how humans work - it's hard to cut time from nice visible things and dedicate it to a hypothetical (at that point) abstract goal like security. Everyone agrees that the latter is important, but it just never ends up getting any oxygen. What's worse, if the team does not know what tightening systems feels like, they don't even know where to start. No "muscle memory" for it.

Maybe at some point we'll get more baseline collective wisdom about it throughout the industry, but it will also take the people signing the cheques (CEO, investors) having a bit more (justified) paranoia and respect for these priorities, and consequently requiring them from the outset. And DevOps has little to do with it - security has to be established as a priority from the leadership levels on down anyway because it necessarily means reducing time spent on more immediately-visible things.

mmatants··on Does Music Help You Become More Productive?
> If someone wants to interact with you, they will definitely find a way to get your attention

Fair enough. However, this does not account for a whole class of subtle little interactions and questions that might be inconsequential one at a time but add up in aggregate to a whole new useful body of communication.

It's when you turn to a co-worker to ask a quick question and open your mouth and then pause because you see them with headphones on, and then give up on asking the question, because the question is actually tiny.

In many many cases, that's how it should be - people deserve their focus time, and we know how much programmer distraction costs. But there is also huge value in team members being available, in the serendipitous "overheard" tidbits that often save duplicated effort, keep the team cohesive and un-siloed. In kind exchanges, not requests to RTFM.

My point being that some (not all!) periods of time deserve to be "open office hours", where people sacrifice some of their focus and invite others to bug them seemingly frivolously. That means taking off headphones and letting oneself be distracted, soliciting easy quick questions. It may seem to conflict a lot of individual productivity advice, but it can help grow the brain trust of the team as a whole.

mmatants··on United States v. Newman Clarifies the Law of Insider Trading
It seems that that would trigger a different set of problems - confidentiality issues, rather than conflict of interest. So yes, still bad, but a different rule-set, perhaps?
mmatants··on [dead]
The issue with things that are intended to be humorous is that they can be interpreted as an escalation. And escalations do not help anyone. Nobody "learns a lesson" this way. In fact, those "creepy people" may get even creepier as a result, too.
mmatants··on The Next Wave
I think it's a transcript of the interview-style video at the beginning of the article, so it kind of flows topic to topic.
mmatants··on The Web’s Cruft Problem
That makes me wonder - why do companies treat design and content as something that does not drive profit? Profit is holistic, otherwise why bother with the so-called "cost centers"? Kind of like a restaurant saying "the cash register is where our revenue clearly ends up, let's just cut out all the other cruft like the kitchen".
mmatants··on Pure UI
And for simpler cases one doesn't even need to detect changes in the model. Just do a debounced re-render the virtual DOM on any incoming event/timeout/network activity:

https://github.com/unframework/vdom-live

mmatants··on ReactCSS – Bringing Classes to Inline Styles
Generated styles?

And great point - these new inline/generated styles are the opposite of what they meant 10 years ago (copy-pasta hacks). Now they are even more powerful than regular CSS, instead.

mmatants··on Engineering Principles and Values
> I didn't grasp anything new or enlightening

Repeating the "obvious" is very important. There is a constant fight against entropy, miscommunication and attrition of experience in any team, and things like these add up in a huge way. The more years I spend in the field, the more I realize the need to "over-compensate" affirming and syncing up on stuff like this.

And aggregating stuff like this into a list is tougher than it seems. This is one of the most balanced values summaries I've seen (for my subjective taste!) - not being too vague, but also not "hard-coding" specific methodologies or buzzwords.

mmatants··on Kantree – A better alternative to Trello
Feels like "Show HN" implies that the submitter is one of the creators of Kantree, but it does not seem to be the case. Maybe a title change would fix that implication?
mmatants··on Simpler UI Reasoning with Unidirectional Dataflow and Immutable Data
Just keep updating everything on every input event! Sounds crazy but with virtual DOM it should be pretty doable at least for prototypes.

https://github.com/unframework/vdom-live

mmatants··on Thinking of using Stripe for your startup? Think again
Thanks in advance! These things help.
← PreviousPage 2 of 6Next →