HNHacker News
TopNewBestAskShowJobs

unabst

1,480 karma · joined June 2, 2015

I am dead.
submissionscomments
unabst··on How to Stop Endless Discussions
I think the evidence points to discussions as naturally tending towards endlessness. Without an end definiting goal or a line drawn, discussions tend to feed themselves to ad infinitum. Basically, the more people you put in a room together, the more they will keep on talking until it's time to go home or someone stands up and tells everyone to shut up. In this scenario, you almost question the person that doesn't talk, and almost urge yourself to join this "discussion". Without moderation, topics could digress anywhere. So you have egos competing to make their mark in this amalgamation of a "discussion" that is supposedly supposed to self moderate and direct itself to a conclusion? The more frustrated those responsible for a needed outcome get, their words and tone become less "fun", as does anyone frustrated about anything said.

So half the solution of "write it down instead" is simply not putting people in a room. Basically, avoiding as much "discussion" as possible.

Whenever you need progress, you need a process. Discussion on its own is hardly a process. It takes determination and skill to have a constructive, time-efficient conversation.

unabst··on Against Essential and Accidental Complexity
Right. But I'm not just moving essential to a different place. I am describing how complexity is made essential or accidental based on where you are in the stack. It actually unifies your theory and Brooks, and I don't what others have stated as arguments against it.

As an accountant staring at a computer, everything about the computer is accidental. Saying simply that the computer is accidental regardless of context is not very useful apart from for refuting Brooks.

unabst··on Against Essential and Accidental Complexity
The crux of Brook's argument is with irreducible complexity which he calls essential, but also qualifies it with what cannot be reduced with technology:

> programming tasks contain a core of essential/conceptual1 complexity that's fundamentally not amenable to attack by any potential advances in technology

Luu is arguing that most of the complexity programmers deal with is of accidental kind. I would describe it as the "incidental to implementation kind":

> I've personally never worked on a non-trivial problem that isn't completely dominated by accidental complexity, making the concept of essential complexity meaningless on any problem I've worked on that's worth discussing.

The OP @ozim that got me thinking reformulated essential as:

> Essential complexity from how I read Fred Brooks is a domain knowledge like what an accountant does

Which I found quite ingenious. Because it's true. Complexity starts from before you sit down to write your program. It's what you bring to the computer. And any non-trivial problem would be dominated by accidental complexity in a computer's implementation space. Unless the computer was already written for accounting.

> essential complexity in Brook's sense is completely unavoidable (in the logical sense).

The moment you interpret any part as "unavoidable" you lose an important neuance. And I was trying to illustrate how "unavoidable" was determined precisely by where you are sandwiched within the existing abstraction layers not of your making.

Even the tax code is written by legislators that are capable of controlling the accidental complexity they implement based on the essential complexity they bring to the table; the requirements they must satisfy before they leave the table.

The accidental tax code created by the legislators becomes essential domain knowledge to the accountant.

And how is this different from HTML or bash or OS programming? Or working with PayPal APIs? The authors, with avoidable choices, determine what becomes unavoidable for the consumer.

The accidental complexity of someone else is now essential complexity to you, by the defintion that 1) it's unavoidable, 2) fundamentally not amenable to attack by any potential advances in technology, and 3) it's the bedrock upon which all of your accidental complexity lies.

So with this model, how do you reduce complexity?

We have layers upon layers of expanding specs. It's not just a computer problem, but a coding problem that also applies to tax law or any other rule making. And it's an entropy problem. Left unchecked, complexity only grows, so how do you fight entropy?

Stacking is part of the solution. Each layer shields all that is beneath it. And for someone using TurboTax, they just see English and buttons and fields to fill. The user is shieled even from HTML.

The front end coder is immersed in the essential complexities of HTML and all of the TurboTax pages are accidental, in accordance with satisfying the essential requirements of the page. But nevertheless, he is shielded from everything below his HTML stack.

We can already see without these layers, the level of sophistication we've obtained with our internet experience may never have been attained. The premise sort of being, TurboTax has never been better. Which I hate to have to admit is sort of true.

Refactoring is another part of the solution that we already do with our code. This may entail remodeling, redefining, and reexamining the problem space.

But we can also refactor our abstraction layers. JQuery was a new layer on top of javascript that was later refactored out by many, as javascript matured (if you could call it that).

In closing, we can refactor code, we can refactor abstraction layers, and we can also abstract more. We need to fight complexity by deleting as much as possible and reorganizing what remains. And part of the solution is finding the minimum number of abstractions that are needed to recreate our solution space.

unabst··on Against Essential and Accidental Complexity
> That's not what accidental/essential complexity mean in Computer Science.

Of course. I was responding to the OP. This thread began with:

> I have different idea about essential complexity and accidental complexity. I think examples in the article are all just accidental complexity.

I was elaborating on that different idea. Everyone seems to be just reverting back to the text book and rejecting the difference not on merits, but for simply not matching.

But complexity is complexity. If we really want to talk about complexity and where the unavoidable part is coming from, then it's from the layer underneath also. When speaking of complexity reduction, you cannot ignore the complexity imposed.

unabst··on Against Essential and Accidental Complexity
Exactly. There is nothing you can do about bash unless you are the creators of bash. In which case, now you are dealing with whatever essential complexity it is you are forced to deal with to create your program. The program itself is all accidental using this model (the model initially outlined by the OP, which converges with the original article).

Maybe "incidental complexity" would be a better term. But the model is the same.

unabst··on Against Essential and Accidental Complexity
You're missing the point which is context. If you're the accountant, the tax code is essential. HTML is accidental. If you're the programmer, then HTML is essential. The outcome of your page is accidental. Accidental is what you have control over. Essensial is what you're forced to work with.

If you're being forced to code in HTML, just as an accountant is forced to work with the tax code, the domain knowledge as provided and exposed as specs, be it HTML specs or the Tax Code cannot be altered. So if the argument is that the tax code is essential complexity for an accountant, then the analogy holds.

To an accountant writing an HTML page for their firm or a one page app implementing some accounting feature for clients, HTML is all accidental. They could use anything else. What is essential to the accountant is accounting.

But since we're talking programming, the situation applied to a programmer: The HTML specs are essential complexity for a web programmer. They must work with it, and cannot work around it. And this is how complexity is passed on through the layers of the system.

And with the case of an accountant needing programming, the line of complexity between them is violated all the time. A web programmer hired by an accountant fails to implement good accounting software by being bound by the essential complexities of HTML. The accountant doesn't care what cannot be done because of some HTML spec. The web programmer must find ways to work around this through engineering, or compromise. This leads to further accidental complexity.

edit/addendum:

> I whip out web dev

The moment you go with web dev, this is the act that now makes HTML specs essential. The only way to escape HTML specs is to use something else, which you cannot do if you're already decided on a web app. Just as the only way an accountant can escape the tax code would be to change professions.

To align the argument with the original article, if HTML specs are half the web app, then the web app cannot be less complex than, say, half. And the only way to get there is to delete everything you did/added which is your page/program. Coding complexity can never break the essential complexity barrier, and accidental complexity in the form of your code is always a positive value.

edit/addendum2:

When adding a framework or library to reduce complexity, there must be a pragmatic replacement/swap of original essential complexity abstractions. The new library is positive, in that you're adding more code, and carries its essential complexity. But when the complexity of, say, jQuery can replace a priori javascript essential complexity, then we can make it out ahead. With the added complexity of replacing complexity.

unabst··on Against Essential and Accidental Complexity
In your example, the tax code is simply the abstraction layer one level down that you have no control over. So to translate your example, HTML specs would be essential complexity and all authored HTML would be accidental complexity to a front-end web programmer.

But this makes complexity a matter of context.

A browser is built using a programming language and uses interfaces provided by the OS and other libraries. This makes the browser accidental. And you can take this all the way down. Assembly is accidental with respect to the processor being essential.

But now we see how complexity flows through each layer. Just as the accidental complexity of the tax code becomes essential complexity for the accountant, the accidental complexity of HTML becomes essential complexity for the web programmer.

And a popular pass time is complaining how much simpler everything could be, only if.

(not sure if this is what the original article had in mind but this model seems accurate)

unabst··on I am lonely will anyone speak to me
You become easy prey for vultures.

On a slight tangent but still related, think overdraft fees. We don't live in a world where the bank will give you money when you need it. They will take more away ever since we invented negative numbers.

I want to live in a world where help is automatically routed to those in need, even without them asking for it.

unabst··on Hell Yes CSS
This is such an oversimplification. Since when did a table contribute to the richness of an application? Most modern sites are built with divs and remain inaccessible.

Tables simplify the code for simple content placement. That's it. It's only one of a long list of requirements to satisfy all sorts of requirements including screen reader compatibility. And if one were to use tables, it's only one of a long list of hacks and non-hacks that would break screen readers.

The root of the problem is with web designers not prioritizing accessibility-friendliness in their sites to begin with, for the basic reason that it prevents them from building the site that they need to build. And "what breaks or doesn't break accessibility" is not part of the spec description and is not enforced technically. We get recommendations, but it's up to us to test everything against everything else and compromise. Not just with accessibility but with everything else as well including backwards compatibility.

unabst··on Tips for a Better Life
“I’m not the kind of person who does things like that”

This can also be not misbehaving or betraying your own values. It's not about you though. It should always be about actions. Not about "is" but about do's and don'ts

Self-identification manifests the ego. You want to identify yourself as others do, based on your actions and not an idea you have about yourself. And especially not an idea driven by impulses. These build the worst egos.

And those who generate ideas about others can be the most dangerous. They will embed an ego they can fight with their own, and even choose to fight it just so they can win.

unabst··on Hell Yes CSS
Exactly.

td supported vertical-align:middle since css1. But you're not suppose to use tables because... hmm. The user sees no difference. Google doesn't care. The browser has no problem with it. It's easier to code. Oh, but it's bad practice... how? I feel like we just listed what qualifies as good practice.

What is it called when following rules only leads to breaking rules? Hint: Sometimes it even leads to javascript.

CSS :)

unabst··on You Should Write a User Guide
It's this.

The developer mindset almost enjoys documentation because you can absorb it fast, in detail, and get on with the problem in the window next to it.

In the real world (TM), problem solving is often a matter of responsibility and a delegation issue and resolved socially. And often for non-developers, the software they are given is suppose to be the solution to all their other problems. So when there's a problem with the software or they can't understand it, a standard reaction is "which number do I call", "train me", or "can you fix this".

For client facing shops, the developer needs to document for customer service. Customer service needs to handle client/user communication. And customer service benefits most from detailed documentation, to allow them to answer user questions without asking the developer.

If this is a mixed collaboration environment, then communication needs management. There are people that want open channels. There are people that don't. And there are people that are offended when their preferences are not met or violated. Management is a requirement.

unabst··on Centering in CSS
I mean, all the comments I got were not about my main points at all.

"No you should do this because of that" is not a valid argument when both "this" and "that" only exist because you created them. If vcenter was part of the original spec, we would have it because the browser publishers would have made sure they fulfilled the specs. We have yet to have it. We are being told valign is a complex feature, and we just accept it.

But you should always model your specs based on use case, because that's who you're serving. Anything less than that is ego and dogma driven development.

And to me, the most disappointing and damning evidence was that w3c does not even author their own web site. They are not users.

https://news.ycombinator.com/item?id=24596769

Being from MIT, I could only imagine how fun a student driven implementation effort could be, and they'd do it for free. I was not alone in 1999 building web pages in an Athena cluster.

Not sure why writing on HN is so often a negative experience. Not sure why I keep doing it.

unabst··on The Strange Case of Dr. Ho Man Kwok (2019)
It's perfectly safe. Soy sauce and parmesan cheese has naturally occurning MSG. MSG is added in campbell and lipton soups, Doritos and Pringles chips, and dozens of menu items at McDonalds and KFC.

Ajinomoto is the powdered form that makes MSG easy. Traditionally umami is extracted through fermentation (as it is in soy sauce) or through konbu (seaweed) or fish (vietnamese fish sauce, katsuo dashi).

The only potential issue, as with any food, is with allergies. Growing up in Japan, there was a rumor that Ajinomoto may contribute to atopic dermatitis (atopy). Still doesn't appear to be any evidence of it [1].Of course, peanuts, milk, soy, wheat, fish, and eggs are the most common culprits, so it's not bad company to be in even if it were true.

[1] https://www.jacionline.org/article/S0091-6749(06)03525-1/ful...

unabst··on Being kind to others is good for your health
> Kindness takes courage.

Not for a kind person. For a kind person it takes courage to be rude. It takes courage to say no, because it's so easy to say yes, because it feels good and it feels right (and I guess is also better for your health?).

I would stop trying to change people or even thinking you can. Someone will pretend they changed all thanks to you, only to be themselves again later when they're done robbing you.

There's a pervasive pattern of the narcissist type surrounded by submissive people and leaving a trail of submissive victims. These people are immediately repelled if they sense you're a waste of their efforts. When you're submissive, they'll take from you and betray you later. When you're not, they don't even ask. They reveal themselves immediately. But they make their money and build their empires by collecting those who yield to them and remain loyal despite occasional revelations of their true character or lack thereof. Trump could easily be seen as such a phenomenon. But most people who are OK with their job will yield to keep it (backed by the psychopathic behavior of corporations and their lack of character, because they aren't people). And many will submit just to make money (even to evil). So there are no shortage of such people to take advantage of. And the more people thrive by doing so, the more we create. Some may even become president.

If you believe you're water, seek water. That is the best approach. Strengthen your water coalition. Stay healthy, strong, and happy. Once you're good, then fulfill your purpose.

unabst··on Centering in CSS
And my point is regardless of how complex something is, unless it's impossible, you can just give the thing a name and hide the complexity under the hood.

Imagine if this just worked since html1:

<div center vcenter>centered</div>

And this since css1:

<div style="align:center; vertical-align: center">centered</div>

Why are we still talking about how to vertical align elements in 2020? That's the question. Having to discuss history as an excuse to why anything is, is a symptom of the problem.

unabst··on Centering in CSS
Vertical centering would work just as horizontal centering works in 99% of the cases as expected. The syntax could be symmetric. We override and adjust as needed. Instead, we have nothing to override or adjust. We're forced to pick a layout system just for a specific feature, and add 5 lines of code that now interferes with everything else.

The argument isn't that it's hard. It's that it could be so much easier. But also, that there just might be a fundamental issue with the philosophy of what could have been just html has evolved into the monstrosity that is css/html/javascript+framework+backend_render... with "the inability for vertical alignment to declared simply" as evidence.

unabst··on Centering in CSS
> It requires a more complex layout

Yes and no.

Yes, because vertical centering can be implemented manually using these available elements as you said.

But no, because all it takes is one of these solutions and naming it "vcenter" under the hood and not having to interact with any of it. And that's exactly what we do using classes or using a css framework that provides for better abstraction than vanilla css. And as the original article demonstrates, there usually is one best practice that checks all the boxes.

It's not that vertical aligning is buggy or that it doesn't work or that it's not possible. There was never a tag for it as if the need wasn't acknowledged, even with the browsers fully capable of doing it as demonstrated by every webmaster that did it since css1.

And to add, complexity is never a reason when you're capable of abstraction. The main issue with CSS and HTML is there is no "let". You're always forced to deal with the specific tags directly. Instead, javascript is provided as a tool for abstraction. So again, it's all possible. We just have to do it ourselves as opposed to there just being a "let".

unabst··on Centering in CSS
> not as easy to figure out what that means exactly

I wholeheartedly disagree. When you see the title "centering in CSS" you know exactly what it means. It's the same old problem everyone has been solving repeatedly for 20 years. It's not about edge cases. It's not about exceptions to rules self imposed by your specific needs. It's just centering inside a box. And the author of the article knows this, and solves it again for us for the nth time with updated techniques.

The issue isn't how complicated a layout is or needs to be. If you were to look at how horizontal center is implemented under the hood, it's going to be complicated, yet that complexity is abstracted away.

It boils down to the simple fact that intuitively when we've had <center> forever, why couldn't there have been a <vcenter> from the beginning? Not even broken, it never existed. It's as if we're being told, "horizontal centering we'll handle, but vertical centering is for you to figure out". Err, why? And figure out based on the tags and attributes provided. Like, they implemented the puzzle but not the solution.

Similarly, why can't "vertical-align: center" just work more often? The fact that a div needs to be a table-cell or a grid, or having the option of using <td> that still works should all be redundant. There is nothing ambiguous about wanting to vertically center.

We're always reverse engineering from a need. Complex needs justify complex code. Simple needs should be simple declarations.

unabst··on Earnestness
No. Narcissists are the popular ones because they can't stop hoarding attention, including yours.

Someone earnest can have an incredible sense of humor and a sharp intellectual mind. They can be kind, well-meaning, and respectful. And, they'll leave you alone. So you might have to poke them with a stick a couple of times.

Social media is populated with narcissists competing for virality on every platform. Highly entertaining, yes. A waste of all of our time including theirs? Probably.

unabst··on Ask HN: Learning about philosophy
Everyone has a personal philosophy, and your path of personal growth is the path by which your personal philosophy is developed.

There are many great interviews with Mike Tyson where he gets highly philosophical. He has some amazing lines, and they just keep hitting hard.

Steve Jobs had great philosophy, arguably laying the foundations upon which Apple was built. Many great entrepreneurs share this pattern.

Einstein and Feynmen are known for their philosophical genius also.

Great philosophy can come from politicians, artists, writers, and even comedians. George Carlin and Patrice O'neal are my favorite. There's great philosophy surrounding sports too. The Last Dance is a great watch.

My only point is, don't marginalize yourself to the field of philosophy. Philosophy is deep thinking, and the ability to articulate and navigate those thoughts. The books under the philosophy section are the thoughts that have nowhere else to be. Great philosophy about computation will be under Computers.

If you're serious about your personal philosophy, then start writing your thoughts down. Then organize them and edit them and pursue them. Pick up books that answer your questions and read the organized thoughts of your role models. Every field has its great philosophers, and more often than not, they're the trail blazers of their field. They will not be found under philosophy.

unabst··on Major Flaws of Human Thinking
"Flaw" is the trigger word. If we rename the list "Common human trends in thinking" then responses would be less dramatic, but also less interesting.

Awareness is definitely the key. If you recognize you're self-projecting, then now you can account for it. If you're aware of what the group thinks, you can be aware of when you're aligned with it. And so on.

Critical thinking is the ability to expand awareness and unimmerse yourself to the point where you can analyze an idea selflessly. Then you can dive in again to reconnect with how everything feels.

unabst··on Major Flaws of Human Thinking
The paradox is "pressure to keep civil" to you may not be the same to me. Numorous times trying to call out someone not civil will put you in the not civil category. That's why systems like HN aren't necessarily encouraging of open discourse. Many don't want to get judged, and judging is all many do, downvoting based on rhetoric and neuance (or lack thereof). And, the achilles heel is the downvote as the not-civil vote, except there is no discourse because you can't reply to a downvote.
unabst··on How I read books: a guide on how to learn
Ergo, learning is stealing. Good students learn alone, and just need goals. Spoonfed knowledge is like processed food. It's clickbaity and likely spread because it makes you feel good.
unabst··on Why Japanese web design is so different (2013)
Rakuten is the original Japanese Amazon. It has everything and is just as cluttered as Amazon. Pages are optimized for maximum spam. Might as well call it the spam UI paradigm.

Here are sites that don't spam.

https://www.au.com/

https://www.playstation.com/ja-jp/

https://kiminitou.com/

And here is a web design aggregator. Here you can see more of the Japanese aesthetic at work.

https://81-web.com/

unabst··on Intel's disruption is now complete
Wouldn't most employees fall under the first category, and managers and executives the next? And employees are paid to carry out goals. while employers take care of the organization and set the goals. With this modeling of the situation, the second group always had control to begin with. They're management.

And there's always corruption and politics where there are humans, be it in the mailroom or the boardroom.

unabst··on Horizontal totalitarianism in life and literature
Exactly. Really wish we could have constructive discussions about ideas again without these vigilantes interrupting every conversation and scaring people away.
unabst··on Horizontal totalitarianism in life and literature
If you have issues with the ideas or know of similar ideas with different names then let's have it.

But what is it with this mind reading and character lynching?

What could be your motivation and why do you even bother?

> spanktheuser

Oh, nm.

What a shame. You seem like a smart bloke.

unabst··on Copyright vs. Copyleft (2007)
I would love if something like this caught on.

"5% royalties due on profits derived from this product."

So if something is given away free, nothing would be due. But if something were used for profit, part of that profit would have to be paid upstream. And that would be profit for that node which, if used the same license, would have 5% of that trickle upstream.

This could be an automatic process and handled through an open registry. Anyone could take anything, register, and then pay their "taxes". If you wanted to donate anything you made, make that an option also.

Of course there are an infinite amount of "what if" scenarios, but that's the gist of it based on the following philosophy:

No one should need permission to copy anything or profit from anything. But they should share their earnings if they "opt in" to capitalism.

unabst··on Sean Connery has died
You're free to disagree or challenge any statement, but character assassination is something else. This is modern witch hunting. This is bullying. What if I had then gone and killed myself. You don't know me. No context should ever justify bullying.

And if you'd asked me whether I am a defender of abusers, I could have writted how I am not. Yet, you've already made assumptions to the contrary.

> your own close-mindedness.

What I said could also be interpreted as open-minded. You just don't appreciate the context in which it was practiced.

To only be able to see things in specific ways to the detriment of others and yourself is close-mindedness, similar to what you have demonstrated with your views.

> If someone needs help, let's help them. Public shaming helps no one.

Take Bill Cosby, since he's been found guilty of acts, not just speech. Do you think Cosby needs any shaming beyond the facts?

If you're going around spewing hate regarding someone who has already shamed themselves by their own actions, what exactly does anyone need you for? And what exactly are you doing?

Sean Connery is the same. What he said embarassed him enough. People already hated him enough for it and punished him at the time.

If you want to help DV victims then let's help DV victims. Shaming a dead Bond does little for your cause, just as shaming Dr. Huxtable will do little or nothing to protect anyone that needs help now. No DV perp is going to read what you wrote and change their ways.

← PreviousPage 2 of 20Next →