Speak English to me: The secret world of programmers

The problem is mainly one of discoverability. The non-programmer in the examples says &quot;simple&quot; when they mean &quot;discoverable&quot;. The programmer says &quot;simple&quot; when they mean &quot;not much code complexity&quot;.<p>Of course you disagree.<p>All the examples - installing and using a package manager, running a command line program - are &quot;simple&quot; from a software point of view, but they&#x27;re not at all &quot;discoverable&quot;. To understand the steps you need to memorise a seemingly meaningless sequence of text.<p>Of course, the programmer has a very strong underlying model of all of this, and so these commands seem straightforward. But even for a programmer, this stuff isn&#x27;t very discoverable. I&#x27;m frequently stumped by man pages, and end up having to hunt down an example of how to use a particular command line application on Stack Overflow. I&#x27;ve been using linux for decades and I still often can&#x27;t find where an applications binaries or config live, and I still very often have to type some magic incantation I found on Stack Overflow into the command line, because my mental model of some subsystem of Ubuntu isn&#x27;t complete enough to know it. None of these things are discoverable - I&#x27;ve got more patience than most in searching Google and Stack Overflow, but it&#x27;s not exactly a desirable way of using a computer. I would prefer it if there was a nice button in the system settings that did what I wanted.<p>When things aren&#x27;t discoverable, they become hard. And people don&#x27;t generally like doing hard things. That&#x27;s not exactly a revelation.

Literally everything I write is in Markdown because it’s so simple to me. I use it for blogposts, presentations, documentation, todos, internet comments.<p>But this article doesn’t strike a chord with me. The author fails to understand that it seems easy to us because we’re familiar with it. Of course we know how to transform it into PDF or HTML. But this knowledge isn’t basic, and it’s understandable that people want to stick to what they know.<p>Here’s an example. Say you had 10000 rows of CSV to slice and dice and extract insights and visualisations out of. All of us would go to the tools we’re familiar with - pandas, R, duckDB etc. But I think the median Excel user probably completes this task quicker and better than the median pandas user. And then if the pandas person is told “oh, just pick up Excel, it’s easy to learn and so useful” they won’t listen. And for good reason! Excel is powerful, but it’s not easy to learn. It only seems that way to people <i>who already know how it works</i>.<p>Don’t confuse the familiar with easy. Just because it’s easy for you doesn’t mean it’s objectively easy.

I find a version of this even with fresh out of college programmers.<p>They just know how to type Java on an IDE, maybe some SQL (using some graphical front end), some HTML&#x2F;CSS. They can&#x27;t operate in a Linux dev environment at all, can&#x27;t use the command line or exit vi or perform any kind of simple shell based automation or use git without a plugin for their IDE.<p>And they also are reluctant to learn because they are self defined into some narrow field that doesn&#x27;t include all this ops trickery in our workflow that they don&#x27;t consider real programming.

As for markdown I showed it to my girlfriend and this is now what she uses for everything. She is a designer and loves that here she does not have to bother with design, just with markup. She hates Microsoft Word with a passion.<p>People who used formatting in any 2000s internet forum know in principle how to use markdown.<p>That aside, I see it as a problem that tech people fail to anticipate the needs of their peers. I know people like that, who dare to say: &quot;Oh you just need to reverse proxy the port on your server&quot; and they fail to realize the person opposite has a face that seems to be assembled purely out of questionmarks.<p>Explaining someone what a reverse proxy is involves explaining them:<p>- what a server actually is (confusingly both the machine and the software)<p>- how&#x2F;that web clients communicate with that server (HTTP)<p>- that on that machine there is software running that communicates a local loopback port (127.0.0.1:7777)<p>- that a webserver can be configured to grab normal traffic coming to port 80 (http) and 443 (https) and forward it to that loopback port<p>- that this is called a reverse proxy<p>Most people are not idiots and will understand an explaination like this. Even if they don&#x27;t they will be happy that you gave a coherent explaination.<p>I just tend to remember myself and how unclear everything was to me when I was a teenager. What explaination would that former me appreciate? Sometimes the most important thing to say is something extremely obvious that helps the person to conceptualize the whole thing (e.g. clients communicate with a server and a server has ports).

I want to point out two additional observations.<p>1. There are a decent amount of software engineers or programmers whom literally aged at the perfect time to organically learn these tools that later became fundamental. If you even touched a computer from the 60s to the late nineties in a engineering aspect at all, you were bound to have worked in a terminal, worked on computers with a single core, worked on computers with very little memory, had to either get comfortable with some lower level tooling or build your own, at some point had to mess with networking or at least understand how packets were being sent and received, seen and gone through iterations of version control and saving your work, automated task using shell scripts.<p>2. While there is a plethora of knowledge, videos, tutorials and flavors of ways to learn these things; the sheer volume and breadth that presents to newcomers is daunting. Yes you can learn Git, but there are so many ways to do it that it can cause analysis to paralysis. Building on point (1) if you learned it early there were only a few ways it was being done or even shared in smaller communities. Too many choices or paths can lead to just using the way someone showed you without digging 1 layer deeper just because you might not know better.<p>All of those things you ‘caught’ by being at the right place at the right time are a privilege. Please don’t look down on people trying to aspire to learn or want to enter into this field that haven’t got there yet.<p>Coming from a family of immigrants and being the first person in my family to graduate college + enter SWE. I cannot count how many times other engineers were rude, made condescending remarks or discouraged me by shoving these expectations in my face as failures instead of taking the opportunity to teach (I was always open to learning).

The problem is most people do not try to put any effort into understanding what they are doing by the computer.<p>When you ask your wife to fetch you from work at 5 you don&#x27;t have to explain:<p>* That she needs to take a car,<p>* That there must be enough fuel in it,<p>* That she has to plan some time for the drive and add extra if traffic is expected on the way,<p>* That she needs to let you know if there are unforeseen circumstances which will likely mean she won&#x27;t make it.<p>And yet for some reason, whenever the topic of doing anything at the computer comes up between us, I feel like I have to start from scratch.<p>&quot;The printer does not work again. Can you help?&quot;<p>&quot;Is the printer on?&quot;<p>&quot;Can you check it, you are better at it&quot;<p>Checking the printer... of course somebody turned it off.<p>I think there is a combination of laziness and probably something else which makes some people treat computers as not their problem. For the most part the companies making hardware and software cater to these people making stuff <i>they</i> care about as intuitive as possible. They are fantastic when it comes to activities that make ads pop in front of your eyes.<p>The trouble is with everything else.

Everything in the post can by explained by &quot;People think the familiar is easy, and the novel is hard.&quot;<p>Judged by the standards of a programmer, yes, the suggested solutions are simpler. Judged by the non-technical coworker&#x27;s standards, no, they are new and therefore scary and harder. You might say, &quot;If they expended even 5 minutes of effort, they would not feel that way.&quot; But that&#x27;s 5 minutes more than just using the thing they&#x27;re used to.

Something I have noticed across the technical&#x2F;non-technical divide is that the concepts of simplicity and difficulty are easily conflated.<p>Often non-technical folk are only interested in &quot;easy&quot; solutions.<p>Technical folks are more inclined to pick simple solutions.<p>The perception of simple being hard mostly comes from simple often eliding things like a GUI which is inherently complex and overkill for a good number of tasks. However users have been conditioned to think mouse == easy and keyboard == hard.

&gt; &quot;Why does it have to be so complicated? I just want to install a program&quot;<p>&gt; &quot;Why would you do that in the command line? It&#x27;s way easier using $Program&quot;<p>A concerning observation that’s slowly dawning on me is that more and more <i>programmers</i> don’t know how computers work. They can write code, build software, and do lots of useful things. But they have no idea how <i>computers</i> work. They’re more akin to lusers as we used to call them than they are to hackers of old.<p>Fantastic at their specialty and the tools they use. But move a button to an unfamiliar place or throw them into a new (but fundamentally same) environment and they’re lost.<p>The realization came a few weeks ago when someone shared The Missing Semester of Comp Sci on HN. It’s full of basic things you’d expect any programmer to somehow magically know … but they don’t learn this anymore. <a href="https:&#x2F;&#x2F;missing.csail.mit.edu&#x2F;" rel="nofollow">https:&#x2F;&#x2F;missing.csail.mit.edu&#x2F;</a><p>Seeing that link shared connected the dots in my mind. I’ve been wondering for months <i>”Why does everyone at work have so many random local environment issues all the time?”</i> … it’s been working fine for me for years. Same code and hardware. ¯\_(ツ)_&#x2F;¯<p>Maybe I’m just getting old and grumpy. I’m sure folks older than me thought “wow kids these days know nothing” when we came on the scene …

If you look at the learning curve of a lot of things that programmers favor over &quot;normal people&quot;, they tend to have a thing in common, which is that they have some sort of step right at the beginning. Markdown, for instance, you have to learn the syntax, and then learn something to do with it in most cases (e.g., put it out on your blog). It&#x27;s fairly easy after that in most ways, but there&#x27;s that step at the beginning before you can do anything.<p>Most people receive the training where opening up Word is not difficult, and then once they&#x27;ve done that, there&#x27;s no step up. They press &quot;a&quot;, an &quot;a&quot; appears on the screen. They have buttons that do things like italicize. The first few steps are easy.<p>It may be the case that after that there is a brick wall in the difficulty curve, whereas the programmer-favored solution is a smooth easy curve for quite a ways. But that first step is sufficient to block most people, and people are often happy to just give up in the face of the brick wall.<p>This is not unique to programmers. A lot of the &quot;maker&quot; disciplines have a similar step curve. A lot of times it&#x27;s just that first step that is the hardest overall. But it&#x27;s enough.

Slight tangent from the original post:<p>I wish &quot;normal&quot; people were more tech-literate. I don&#x27;t think they realize just how much of their autonomy they&#x27;ve given up by choosing to use Microsoft Products&#x2F;Reddit&#x2F;Twitter&#x2F;Spotify&#x2F;Facebook&#x2F;TikTok&#x2F;Apple Products&#x2F; etc.<p>We&#x27;re at a point where now the average person depends on several layers of technology that they can&#x27;t even conceive of, and often the companies building that technology don&#x27;t share their political interests. But then the average person expresses frustration at having to use open-source alternatives (which is completely understandable when the open-source alternative is definitively worse!).<p>Basically, for me not understanding how technology works when it&#x27;s so central to our everyday lives just seems baffling. I suppose someone could say the exact same thing to me about not understanding how my car works, or how to grow my own food. Maybe technology seems easier to learn than agriculture? But then <i>of course</i> it&#x27;s easier for me, I&#x27;m a professional programmer. So I try to have a lot of empathy for everyone who doesn&#x27;t understand technology, especially my mom when she doesn&#x27;t know how to convert a PDF.

&quot;Normal&quot; people see other people as technologies - you sort of give your problem to the person, maybe mix some money in and then the problem goes away. This is how the relationship with people like lawyers, doctors, salespeople, etc, etc work.<p>They know that engineers (and programmers) are in the same <i>rough</i> class as all the other professionals. These conversations showcase the confusion as they try to figure out what problem programmers are there to solve. Other engineering disciplines also suffer from this - engineering is a subtle art. Nobody knows what we actually do except the rest of the brotherhood :(.<p>The first example is a really good showcase. They really don&#x27;t want to be walked through how to solve their problem. The point of the specialist is supposed to be that they solve the problem in exchange for payment. They don&#x27;t understand that programmers are really all about adjusting the cost of taking action rather than acting directly.

My two cents, as an aspie programmer, we think too fast.<p>Programs like Microsoft Word are amazing, even Richard Stallman himself has praised it. So there&#x27;s nothing wrong with Microsoft Word, but some people just feel like a GUI is a bottleneck.<p>I&#x27;m speaking for myself here first and foremost but I know there are literally dozens of us. ;)<p>Why choose markdown over Word? Why choose CLI over GUI? Why choose Linux over Windows? Because it&#x27;s just quicker, it allows me to get my ideas out faster than the alternative.<p>But I&#x27;m not saying we don&#x27;t have some work to do on inter-personal relations and how to deal with end users and clients. We definitely do and I work on that every day.<p>I think it comes down to memory capacity. If you can remember several languages, or command line syntaxes, or programming languages, then you can use that to get the same results as any GUI program, much quicker.

Similarly, many non-programmers can do tasks that some programmers must hire a professional for (like repair drywall, install a ceiling fan, basic car maintenance, etc).<p>Empathy is one of those skills that is as, or more, valuable than any particular programming language.

As an intensely tech guy I completely despise the tendency that some engineers have to speak in ambigu-ese and tech-ese making less reacheable what the fr*eak they are talking about and establish themselves as &quot;essential experts&quot; when they could easily speak in normal-ese with minimal effort making concepts reachable for colleagues.<p>BTW this can happen to any field, not just tech. It can happen with intellectuals, philosophers, medical doctors, blockchain lingo, AI lingo, devops lingo, telecom lingo....<p>Fortunately! Now we have AI which is insanely good at summarizing and explanning anything like I&#x27;m 6y&#x2F;o so that little expert trick just got massively nuked and has its days counted.

I used to think that I find tech stuff easy because I&#x27;m used to it (and there&#x27;s certainly some truth to it), but if that was all of it than I would expect myself to behave like tech illiterate people in domains that are foreign to me.<p>And yet this isn&#x27;t so.<p>The reality is that peoples problem solving skills are absolutely atrocious. They don&#x27;t even try to figure shit out. The maximum number of inferential steps the average person is willing (or able?) to make before throwing their hands up and exclaiming &quot;this is impossible&quot; seems to be somewhere between 0.5 and 2.<p>There seems to be just enough stuff you can do without having to ever really think for yourself that people are content with not understanding.<p>This is so far away from my own experience that I really struggle with understanding it. Obvious knowledge gaps and noticeable confusion are two of my biggest motivators. I cannot stand not understanding. It feels like giving up agency.<p>Wow. I got quite angry there for a second. I guess I need to examine that frustration a little more.

Yeah, I feel this. I recently added a .tool-versions file to a website repository (that non-programmers need to edit) and updated the README to say &quot;install asdf (<a href="https:&#x2F;&#x2F;asdf-vm.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;asdf-vm.com&#x2F;</a>) and then run `pnpm install`&quot;. And then I saw people try to follow the instructions and start needing to install Xcode, then Homebrew, etc., and it took forever. I think the right solution is to give them a 1-click cloud IDE with the repository loaded and a live preview running in the background.

There are some good points raised here - it does feel at times that development is getting further and further from the end-user.<p>And I find myself wondering if I’m beginning to serve technology rather than the other way around.

This reads to me like very blinkered &amp; elitist thinking. Repetition makes things easy, we are good at what we practice doing. A normal computer user rarely needs to do something that might be more efficient in markdown, command line, whatever, so their speed in doing that will be slower compared to a graphical interface.<p>Normal computer users want programs with dropdown menus and they are faster with those than we are when we have to look up a command or function that we rarely use. I know people who can filter &amp; pivot a complex dataset quicker in Excel than I can in SQL.<p>I think it is safe to say that most programmers occasionally encounter something they need to Google for and dig through some stack overflow posts to find the syntax. That would be necessary almost constantly for a non-programmer and it&#x27;s just not an efficient use of time.

As people are mentioning a lack of Linux knowledge; is there a good course on this?<p>two things; - I think it boils down to people not having &#x27;poked around&#x27;. I grew up on DOS &#x2F; early windows, when messing about, learning commands, configuration files was needed to install and run games (or new hardware). New game, new challenge. This learning process was part of the use of a computer to me. It gave me enough confidence and knowledge to &#x27;try things&#x27; in later Windows or software if things were not working. To most people i&#x27;m a &#x27;computer guy&#x27;, yet when it comes to Linux &#x2F; unix &#x2F; mac I have no idea how to get around.<p>- being overwhelmed &#x2F; debilitating alienness (for lack of a better word), when they dont have adjacent knowledge &amp; confidence. It&#x27;s not just the transfer of knowledge, but often a çomfort of familiarity that is needed. My wife was a basic computer &#x27;user&#x27; who would panic or blank out when she got simple technical instructions or something went wrong. I quickly learned that it was more helpful to show her we can just poke around, and it&#x27;s ok to not completely understand something. We talked about how to communicate computer problems, and effectively use google. She got over the &#x27;deer in headlights&#x27; syndrome, and now actually welcomes any new computer topic - while working in IT service desk!

This used to bother me before, but then I realized, &quot;this is why I get paid the big bucks&quot;. Now, I see my &quot;unreasonable&quot; requests as a sign of how much I&#x27;ve progressed in my field, even relative to some of my peers, who can&#x27;t do basic devops.<p>It&#x27;s easy to forget how many countless hours I spent learning how to Google for the right command line args and picking up little tricks here and there to chips at problems until I&#x27;ve solved them. Take a deep breath and give everyone else who can barely use their keyboard and mouse to do their work a break alright. Not everyone enjoys bashing their head against the wall to solve these things the &quot;easy&quot; way.

The author argues that markdown is the best way to write text. I know many people who argue that LateX is the best way to write text, and they also have arguments.<p>As a programmer I sometime prefer the world of clickety-click GUI instead that of command line. Doing something in a visual way, requires no knowledge. You just discover how to do things as you do them. Using the command line requires me to learn paths, steps, command line arguments, the order of the command line arguments and also memorize them.<p>Some times I prefer the command line.<p>I know that for some folks VI or Emacs is better and more productive and faster, but for me Visual Studio is that and more.<p>Maybe there isn&#x27;t one objective truth, and for some persons the command line and text editors is better and for other folks the visual stuff is better.

It&#x27;s a little depressing that after all of the work the industry has put into graphical interfaces and making software easy to use, the mark has been so widely missed. It seems to me that a big part of this post boils down to people frustrated (in some cases literally to tears) at their inability to make the machine do the thing they need done.<p>I don&#x27;t have a solution, but I think we have two big problems: the rigidity of the GUI (it&#x27;s difficult to combine operations, in some cases impossible) and then arbitrary gatekeeping of features for dollars (why can&#x27;t the free Acrobat export PNG files?). For every tool like Excel, we have another &quot;simple&quot; tool that is nearly only one possible workflow.

This can be a simple frequency-of-use issue. Non-programmers might need a command-line solution once or twice a year. It&#x27;s hard to remember a series of steps that you don&#x27;t frequently perform.<p>For example, you can theoretically know how to change a tire, or how to use Photoshop to replace a color in an image, or how to troubleshoot a printer. But you only run through that series of steps occasionally, when there&#x27;s a specific problem to solve.

I wrote an essay once that was nominally about using Pysimplegui to get folks to use your software, but is really about understanding ways to make your software accessible to people without your level of coding ability:<p><a href="https:&#x2F;&#x2F;cushychicken.github.io&#x2F;python-guis-for-heretics&#x2F;" rel="nofollow">https:&#x2F;&#x2F;cushychicken.github.io&#x2F;python-guis-for-heretics&#x2F;</a><p>Might find it interesting.

This has the same energy as programmers who can&#x27;t understand why other programmers won&#x27;t use vim. &quot;It&#x27;s so simple, though!&quot;

&gt; I try and try to explain that this arcane system of monochrome text and rendering steps is ACTUALLY easier than editing in Microsoft Word, but my pleas fall on deaf ears<p>I know my way around Markdown, but I just don&#x27;t like it. I&#x27;d rather directly see what I&#x27;m working on rather than a weird approximation.<p>(I don&#x27;t like hidden or direct formatting either, which is why I do sometimes use Markdown)

I&#x27;m trying to decide if this is parody or not.<p><i>I try and try to explain that this arcane system of monochrome text and rendering steps is ACTUALLY easier than editing in Microsoft Word, but my pleas fall on deaf ears.</i><p>Easier for you, who probably has an auto-activating mode in your text editor that highlights Markdown. Not easier for someone whose only plaintext editing tool is Wordpad. Not easier for someone who can hit command-i to turn on and off italics as easily and thoughtlessly as you type <i>.<p></i>And of course it is a simple program, but whenever the first step is opening a terminal, it is no longer simple*<p>To you, the terminal is a comfortable place. You have learnt all the arcane incantations, including the ways to make the terminal help you craft and remember them. To them it is a mystifying place, with little guidance, and the possibility of totally fucking up their computer if they type the wrong thing.<p><i>I tell them to execute the simple and easy step of running $PACKAGE_MANAGER install $PROGRAM, and they don&#x27;t want to do it.</i><p>And then you list examples of exactly how you <i>have</i> learnt all the arcane incantations. You <i>have</i> ten different package managers on your computer already, and know how to use them.<p><i>&quot;Can you help with my printer&quot; &quot;no&quot;</i><p>Fair enough, really. Drivers suck.<p><i>What was the point of writing this post? I don&#x27;t know. [...] Maybe I just need to have a little more empathy (or is it sympathy?) for normal people.</i><p>Yes.<p>Find someone who refuses to use your cryptic incantations, and find out what they&#x27;re really good at. If you can find someone who&#x27;s <i>frighteningly</i> good at a thing, who&#x27;s been doing the thing at a professional level since before you&#x27;re born, that&#x27;s the best. If it&#x27;s something you have <i>no</i> interest in doing yourself, that&#x27;s even better.<p>Ask them their stories of the time they had to work with someone who was completely clueless of <i>their</i> craft. Ask them how they do something that looks impossibly complicated to you with next to no effort. Ask them to walk you through doing one of those things in enough detail for <i>you</i> to do it. How immensely tedious does this start to sound? How many times do they use a word you&#x27;ve never heard, or a word you&#x27;re familiar with in a way that is pretty clearly having a very specific meaning to their craft that is not the same as normal usage? What tools do they refer to; how many of them do you have casually sitting around your life, and know how to use with even the vaguest competence?

Linux sysadmin here. I’ve come across plenty of documentation, I’m almost certain was written by a dev, where it’s assumed I know the correct command line usage or concepts. I know a lot more than the average end user, but I’m _not_ a dev, either.<p>And please… (to those writing docs) always include examples. So many man pages lack examples; it can be very frustrating.

Interesting how more deficient designs are promoted as better alternatives just because the author is used to their ineffectiveness<p>Like the cli example &quot;explain how simple it is to just convert -density 300 input.pdf -resize 50% output.png, and I&#x27;m met with a blank stare&quot;<p>Why would an unsuspecting user ever need to remember (or worse - look it up) that density is &quot;-density&quot; and resize requires explicit % when a GUI app can show the most common flags right there, with in-band help and validate your input (was there a typo in a file name and inupt.pdf doesn&#x27;t exist?) in real time?<p>Or the markdown example with tables, which are especially painful to edit one you add just a bit of complications like formatting, which break your tabular alignment, practically requiring you to use both md and formatted output Why would you wish regular users this pain?

&gt;&quot;Oh, you&#x27;re a programmer, Can&#x27;t you do $THING&quot;<p>I&#x27;ve been asked by others to install software, repair PCs, repair laptops and even modify or replace firmware on phones. Sometimes I did it, if I had time. But for my personal needs, I always called a technician or went to a repair center.<p>As for programming tasks, I did many: C++ desktop software, Windows device drivers in C, embedded software, websites in HTML + JS, video games, mobile apps, hacked Android kernel modules and libraries, web backend, web frontend, microservices.<p>If you have the time to learn the business domain, learn tools, frameworks, libraries, APIs - you can work on anything. &quot;Doing&quot; things is different, because some projects are quite huge, impossible for one person during his life time.

Isn’t this applicable to pretty much <i>all</i> domains of knowledge? ‘Just change the oil yourself, it’s easy’, says the auto mechanic. ‘Just add the circuit yourself, it’s easy’, says the home electrician. There’s a term for this, but I can’t recall it.

They probably don&#x27;t know how to use Word as well as you imagine either.<p>There is often an office Word or Excel expert, despite the whole floor spends all their time in those apps. The expert is just the person who was willing to poke around the app or Google things.

I think tech is getting more complicated for no reason. But also in the &quot;techy&quot; side. Look at web development: it used to be simple, now it&#x27;s mindbogglingly complicated. And I don&#x27;t see a good reason why...

&gt; “Can you help with my printer” “no”<p>So true. I can’t even help myself with the blasted thing.

Not really a novel observation, nor surprising.<p>The secret world of auto mechanics: “Just change the air filter.”<p>The secret world of electricians: “Turn the circuit breaker off and back on.”<p>The secret worlds of chefs, carpenters, doctors, lawyers, … I could go on and on. Why would programmers expect people not invested in programming to know this stuff, or care?<p>I only care about ignorance of jargon and specific skills when demonstrated by so-called professionals. A “programmer” who can’t install from the command line seems like an auto mechanic who can’t open the hood.

It&#x27;s important to consider your audience and there are all kinds of tools to bridge the gap. If you really want someone non-technical to work on a Markdown file with you, show them a nice online Markdown editor with a live preview. If they asked me how to convert a video, instead of recommending ffmpeg I&#x27;d recommend an ffmpeg wrapper like Handbrake.

I feel like github is not the right place to put a blog, reading any text there that is longer than single line gets me eyestrain.

Once &#x27;bash&#x27; is replaced by &#x27;aish&#x27; and its avatar &#x27;SAIri&#x27;, users will be able to do the tasks that are not immediately clickable in the next menu, by just asking SAIri. At that point, your non-programmer friends won&#x27;t be asking you stupid questions anymore! :-)<p>Unless &#x27;aish&#x27; has crashed.

The divide between techies and normies isn&#x27;t clear cut. Some of us are &quot;double agents,&quot; observing both worlds from the inside. I&#x27;ve been using the command line since 1982, and am a heavy user of markdown.<p>&quot;It&#x27;s simple. Here&#x27;s a terminal command you can use.&quot;<p>It will return an error message on the first try. After much back-and-forth over chat, I&#x27;ll come to your cube and see for myself that it returns an error message, then find a few more commands and settings that were needed to make it work. The same commands won&#x27;t work the next time.<p>&quot;Just use markdown.&quot;<p>The 80&#x2F;20 rule looms large. Markdown will produce a readable document, but I won&#x27;t be able to tell you how to make it conform to an existing aesthetic style, or even know where to look for that information.

This is just kind of an elitist (kind of!) rant by a coder - all of which I can understand and mostly agree with because I’m a coder too. But any specialist could make the same case for people outside their area of expertise. Some people prefer manual transmissions in their vehicles and will chit on people who drive automatics.<p>The difference being most software&#x2F;tech workers largely make their salary from non-tech savvy consumers so I don’t know, maybe some more perspective is needed in dealing with “normal people”.<p>But also helping out with printers and stuff is lame, as mentioned I understand where author is coming from.<p>Edit: I guess my point is - rants are totally fine if labeled as such but this doesn’t seem very constructive to me. Hopefully us tech savvy individuals can help level up everyone else

For normal people (non-programmers) computers are pretty terrible. I&#x27;m kind of curious what happens when everyone gets a Jarvis-like assistant that can do the scary stuff (open a terminal, type some commands, or possibly code up a nice UI in seconds) based on natural language requests.

&gt; &quot;First off,&quot; I reply, &quot;No. And second off,<p>This is a super condescending thing to say. Let&#x27;s say you&#x27;re a lawyer telling a client why you can&#x27;t do something. The language you&#x27;re using is pretty harsh.<p>&gt; Maybe I just need to have a little more empathy (or is it sympathy?) for normal people.<p>You are also a &quot;normal person&quot; I don&#x27;t understand why developers sometimes think they are gods or something.<p>&gt; Can you help with my printer. No<p>No explanation on this one at all? That, again, is a rude response.<p>I&#x27;ve been saying this for a while, but the pay we provide to developers was a mistake. It has created a class of people that think they are gods. Come down from your soap box, learn real empathy, decide you are a Normal Person yourself and get rid of your condescending attitude.

<i>&quot;Oh, you&#x27;re a programmer, Can&#x27;t you do $THING&quot;?</i><p>This is the one for me. Yes, <i>yes</i> I could.<p>If I spent a year learning how to do $THING.<p>So after that exchange, I&#x27;m either stupid, or more likely <i>&quot;Well, if you didn&#x27;t want to help, you could have just said so&quot;</i>.

Loved this. I think there are many more characteristic cases of programmer-muggle “lost in translation”.<p>On a tangent,<p>&gt; Can you help with my printer?<p>Related Ask HN: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=35165560" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=35165560</a>

The one thing I wish people would get over is their fear of the terminal. This isn&#x27;t to suggest that they should use it, never mind embrace it, but they should not have an adverse reaction when someone gives them specific insructions to type in a command then copy+paste the results while providing technical support. Such insructions tend to be much more accurate than sending people on a GUI scavenger hunt, particularly when you consider that GUIs tend to vary in time.<p>Alas, as the article states, it is as though you are speaking a different and very intimidating language to non-technical users so the end result is nowhere near as positive as it should be.

Programming isn&#x27;t somehow unique in this sense.<p>Anytime you speak to any subject matter expert they&#x27;re likely thinking &quot;ok what&#x27;s the simplest way I can phrase this for this idiot&quot;.<p>Not sure what the solution is beyond being kind &amp; understanding &amp; patient

I do feel it necessary to point out that IT and software engineering are largely diverged fields. Additionally enterprise and consumer IT are very different too. So if random person ask how to share files your answer can&#x27;t be Sharepoint or NFS server or something, and even if it was the answer you would put random web developer to set up that Sharepoint site or whatever. Similarly if I as a software engineer have trouble with my work workstation, I don&#x27;t waste time to try to debug it myself, I go to our IT dept and get them to fix it.

Every profession has its own language and jargon. Even the offices I&#x27;ve worked at each had their own unique jargon.<p>For example, there was one office where the engineers were affectionately known as &quot;swine&quot;. (I&#x27;m not sure how that came to be.) If an engineer did some particularly clever piece of engineering, the ultimate compliment was to call it &quot;swinish&quot;.<p>To an outsider, this made no sense at all, but it worked for us.

My children are a fine example - they&#x27;re teenagers now, and they have had more access to tech than most people (thanks to Dad [me!]). Yet they barely know how to do more than Word, and don&#x27;t understand the concept of a text editor vs rich text editor vs word processor.<p>The problem isn&#x27;t them, it&#x27;s us.<p>Why DO we expect &quot;normies&quot;, as it were, to understand Markdown, text editors and the holy war of Plain Text?<p>Why are we going backwards with our tooling?

Man learns outside world exists, is annoyed by it.

<p><pre><code> &quot;Oh, you&#x27;re a programmer, Can&#x27;t you do $THING&quot; </code></pre> I always respond with &quot;I don&#x27;t really know how to do $THING. It&#x27;s kind of like asking the piano tuner to play a sonata. They might be able to, but just because you can tune a piano doesn&#x27;t mean you can perform a piece of music on the piano.&quot;

I frequently think to myself, every programmer should be forced to suffer as a user. The weird, risk averse behaviors of users will begin to seem reasonable when confronted with the actual experience of using computers.<p>&quot;Simple&quot; means &quot;uses abstractions that I&#x27;ve learned by trial and error but can&#x27;t explain.&quot;

&quot;Oh you&#x27;re a programmer, come this to this start up idea you can do after working 9-5 for zero pay&quot;

Was this written by a high schooler?

I think the author lacks a lot maturity in collaboration. If you are collaborating, you have to put your preferences aside and use the tool that works for the majority. If that tool is MS Word, you just swallow your nerd pride, and use Word.

After a decade of this, i convinced my mother in law to buy a MacBook and genius bar support. No, i won&#x27;t fix your printer. Sorry that i figure this out quickly. LMGTFY got me in a lot of trouble with my family...

Any article like this always has to the the “Can you help with my printer?”

We as an industry really need to be a whole lot more intolerant of ignorance. People learned how to drive, they can learn how to use a computer.

Yeah, we consume objects and fork children without even thinking about how that might sound to a non-programmer.

&gt; Can you help me with the printer?<p>LOL. No, because I can never get the ducking things to work either.

&gt;&gt;&quot;Can you help with my printer&quot;<p>&gt;no<p>Can you do my taxes for me? I hate printers as much as you do.

I really wish people would stop writing blogs in naked GitHub repos.

most devs I&#x27;ve worked with in my career are absolutely terrified of CLI, and if their IDE doesn&#x27;t hold their hand they are completely worthless.