Hacker Newsnew | past | comments | ask | show | jobs | submit | more BiteCode_dev's commentslogin

Adults don't want to behave like they used to behave as kids.

They don't want to spontaneously talk randomly about something to an unknown person, because that comes with risks like rejection, looking like a fool, being labelled in a certain way, associating with somebody boring/annoying/leeching, etc.

Kids takes way more risks, including social risks, because they don't know those are risks.

I guarantee that if you go to clubs or public places you enjoy, and you bring out the kid in you (at least the part that doesn't bring chaos), you will make friends eventually. Not immediately, but keep at it, and it will happen.

However I noticed many adults don't actually want to live the process of making friends. Even without risk, they don't want to make the effort.

Because here is another thing that adults don't have and kids have plenty: energy.

And it turns out making friends require a ton of energy, because while you can be yourself and make friends, you cannot "be on your own" and make friends. You can't live a perfectly scheduled life and make friends. You will have to get out of your bubble, move things around in your day, welcome the unexpected, and interact. You will have to discard something in favor of it. And you will have to do it again and again because most people are not a good fit to be your friends.

Kids do that all the times, without even thinking about it.

Forget about the missing opportunities, it's only the tip of the iceberg, and it can be overcome by getting out of your way. I have friends that are 10 years older or younger. I made friends after my twenties and after my thirties.

Hell I'm going forty yet I made a new friend 2 years ago, and we are getting pretty intimate at this point. My mother is almost 70, and she is still dating.

But when I feel like inviting new people into my life (which I don't always do, right now I have closed doors, I don't have an infinite reserve of private life to share), I will invest in it. I will accept the cost.

Because making friends is not free. Just like sex is not free and speaking your mind is not free.

Kids don't realize the cost, and bare less the weight of it, but we are very aware of it.

Making friends don't "just happen naturally" when you are a kid, there is a process.

But the process is seamless to kids, while it requires effort to adults.


> Kids takes way more risks, including social risks, because they don't know those are risks.

> Kids do that all the times, without even thinking about it.

> But the process is seamless to kids, while it requires effort to adults.

Clearly your childhood was nothing like mine or that of a lot of other people here.


> Adults don't want to behave like they used to behave as kids. > They don't want to spontaneously talk randomly about something to an unknown person, because that comes with risks like rejection, looking like a fool, being labelled in a certain way, associating with somebody boring/annoying/leeching, etc.

> Kids takes way more risks, including social risks, because they don't know those are risks.

It sounds like I never was a kid.


Indeed. Treating every topic as something I should get my mother to do over the phone while driving gives wonderful results. It improves communication, documentation, code, stacks and logistics.


As usual late to the party, but author here. AMA and all that.


You are a great example of the too good to be helpful crowd.

"Things should have a good doc and you should read it".

I could not have come up with a better example in the article.

This is just perfect :)


Honestly, based off what you said, in my opinion you clearly lack credibility.

The very least you could do is properly quote what I actually said instead of poorly paraphrasing, and then holding that paraphrase up as an example (with a different context). That's no better than putting words in other peoples mouths, its just flawed reasoning, and the tactic comes off as plainly manipulative and biased.

If you read and comprehended what I said, and knew what good documentation practices are, you'd agree if you had the experience.

Every single time I've seen a developer say differently and get their way, its resulted in project cost overruns by integer scaling factors greater than 1, many times in the double digits, assuming the project even completed (some don't).

Availability of good documentation on existing systems makes and breaks project budgets.

I really don't see how you can reasonably think this is a good example, let alone a great example. You of course are free to think what you want.

Fundamentals are covered in Chapter 31 of the Limoncelli books (TPOSA) covers the broad strokes, and Redhat Documentation pre-IBM takeover are examples of good end-product from proper documentation practices.


to quote the original article: And these people, there are the ones telling the average rest what they should do


Em, this isn't meant as a snipe but has to be said because you clearly didn't read and comprehend.

Read what was said, and make sure you look up the definition of words like over-generalization beforehand (its a logical fallacy). If you can't pass reading comprehension at a grade school level, there seriously is almost no skilled job your suitable at. This is basic fundamental stuff. You need to do this for almost everything in a professional environment.

> And these people, there are the ones telling the average rest what they should do

Following that reasoning, you can literally claim anyone who communicates anything is telling someone what they should do, and the author tends to fall into this bias to group people doing just that. So anyone they want or perceive as negative then falls into this group which in fact encompasses all humanity (because communication is inherent in almost everything we do). This is literally in the definition of over-generalization, which is what I said (if you go back and read). Its also very common and manipulative tactic in identity politics often used for malign infuence against those that don't critically think to dupe them.

Unfortunately, this lacks any kind of rational thought, is biased and follows flawed reasoning, and as a result lacks any kind of credibility, and rightfully so.


Nassim Taleb has a great bit on it: characteristics of "natural" systems tend to settle on gaussian distribution on a long enough time frame. Weight, life span, force, height, skills... On the other end, systems that we have created have metrics that tend to not follow the normal law: money, electricity consumption, size of houses, etc.

It's not a perfect match and I'm not trying to write a white paper on anything. It's just a way to warm up the reader to the essay point.


In the BBC interview, Musk says they are thinking about changing the label to "publicly funded".

Seems like a good compromise.


Not it's visible because the victims have more money than the average one, and they are not used to be attacked, so it makes a lot of noise.


Same, I really prefer the design on the left. Easier to see things, and it makes you feel you can click on elements.


> it makes you feel you can click on elements

This is not intrinsic to the design, just a force of habit. The design on the right looks perfectly clickable to me.


I usually champion the "let's start with the UI" state of mind in every company I go.

This has several benefits:

- it forces to confront reality of the problem and field

- you have to talk to people, and understand their needs

- you almost get your backend public API out of it for free

After that, you don't really need to do full top down, you can split in subsystems, and works on small parts of those subsystems.

It doesn't have to be a good looking or sophisticated UI. It can be a ugly, as long as it's practical and validated by the end user.

But this works only well the if the problem can be well defined and you know how to solve it.

If you need to figure it out, top down doesn't work as well.


A downside to this is that some types of stakeholders lament the apparent glacial state of progress backfilling a UI with functionality.

A tick/tock of UI/functionality keeps those people from getting depressed during demo meetings.


If you have demo meetings that matter, you likely have a designer, in that case the UI won't be ugly.


Demo meetings that matter, now that's an anti-pattern if I've ever heard one. Only UI work makes for a snazzy demo, anything else will bore stakeholders to tears (and you of course need stakeholders if the meeting matters). The backend can be completely mocked out and stakeholders wouldn't even realize. All demos do is bely progress and make milestones seem closer or farther away than reality. The only "demo" that matters is the actual product launch.


demo meeting matters for several things:

- reassuring the people that pay the bill

- get PR feedback

- give a concrete objective with a deadline to the team

But like a lot of things, it's not useful for what most people think it's useful.


All of those things can be done through other mechanisms without distracting engineers with a dog and pony show.


I have always had great success when systems are designed from the UI first. It really helps you break a new business case down to the point where the backend code just starts writing itself.

I suspect you are coming from a design background because people who have never built a UI before are always very suspicious of this suggestion.


I don't come from a design background but my father drilled into my skull that nobody cared about my beautiful skills at work. They cared about their problems and if I could solve them.

Coding just happen to be a mean to solve their problems, but they don't understand code, and I don't understand their problem.

After a lot of frustrating client/dev interactions, I came to read "don't make me think" from Steve Krug. I realized the UI was the only language I shared with my customers to start a meaningful discussion.

This turned out to work well, and got me paid, so I sticked to it.


This is how I start with libraries. How do I want to use it, and start with some code that will eventually compile. It acts as an integration test too. But this starts to expose issues earlier with my understanding. Then if the interface doesn't work, it's easier to fix earlier.


I know it's passe, but I generally like to start with a set of requirements first. In the old days, when we were doing XP instead of agile, we didn't feel the pressure to "code something, anything." Now, unless I check in a couple thousand lines of code per day people think I'm slacking.

But... not trying to say "build the UI first" is a bad choice if it works for you. I do mostly backend work on "high trust" transactions, so I tend to look at the API first and see if it matches the requirements i have at the time.


A good many times the customer doesn't spot important issues until they see it in a UI, preferably interactive. The design process is done best with a combination of formal written requirements and mockups/demos.


For some applications, like an API-driven backend made to serve other applications, you can consider that the API itself really is your UI. It's how your users interface to your code. Your users just happen to be other developers whose code had it's own UI too, maybe a text or graphical one or maybe another API.


Good point. I was interpreting "UI" as "GUI".


Exactly. A web api, a CLI... It doesn't have to be graphical.


XP as I remember it was about implementing one customer-relevant feature at a time. This isn’t too-down or bottom-up, it’s doing a thin vertical slice. There shouldn’t be code that isn’t used or buttons that don’t work.

We did work from a designer’s mockup, though.


I don't think that's XP.


Trouble is, how do you get this set of requirements?

The UI is the answer to that.


The UI [GUI, API, CLI, etc] is a statement in the "solution domain." By "requirements," I mean a problem statement.

"A form with three text inputs labeled street, state and zip" is solution while "the system should allow the user to specify an address" is a problem statement. (And ideally it should be more detailed with respect to its context: "The system should allow a user to specify an address associated with a delivery record, associated with the user's id.")


The problem is generally poorly perceived and expressed by the client, and badly understood by the dev.

So the UI is the best road to build one in collaboration with the client.


I coach Product Owners the same way when trying to create a backlog.


Same.

Most of my readers come from HN, reddit or substack itself. Now it's mostly Python so it makes sense a tech oriented medias will be reading more about it.

Still, the ban on substack by twitter means that, while a #python tweet gets some view, the same with an article to substack tanks bit time.


I'm curious how you're dealing with Reddit: some of the mods don't even respond to a direct message; they just say "read the guidelines." And then their auto-mod deletes your post.


I have a very old account that has been mostly posting quality content. I also take great care of writing content that I wish I would I read myself.

So when I post it, it's congruent.

Basically, either you find a way to cheat, or you climb the ladder. I'm terrible at cheating.


If you post the entirety of the content to Reddit itself and just leave the link in your profile, you can often get away with it


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: