10 ms·
How do you do, fellow web developers? A growing disconnect
- freetonik 2y agoThanks for posting. Earlier I submitted the original video which motivated me to write this blog post: https://news.ycombinator.com/item?id=42461182 https://news.ycombinator.com/item?id=42461182
- simonw 2y agoGiven that every inch of that YouTube gameshow is "Sponsored by Jetbrains" (their logo even shows up multiple times on the spinny wheel thing) I'm not surprised they feature screenshots of Jetbrains IDEs showing off their type-related features.
- sesm 2y agoAlso, it makes sense to target this show at complete beginners, because experienced programmers rarely change their tools.
- k__ 2y agoNot a fan of these "old man screams at cloud" posts, but I had a similar experience. Suddenly, everyone was talking about HTTP APIs, when they said API. With the rise of IOS and Android, I expected the mobile devs would build something better than HTTP, without all the cruft from the past. But somehow that didn't happen. Now API is synonymous with HTTP. Strange how things turn out in the end.
- penjelly 2y ago> Suddenly, everyone was talking about HTTP APIs, when they said API. I always try my best to delineate for people asking, but often I find they only care about the web API case, so me harping on about how an API can be used to control a robot OR a web server often just confuses them more.
- Kim_Bruning 2y agoI ... I may have made a web API that can control a robot? Err.... I realize I'm not helping. I'll see myself out.
- alibarber 2y agoI had the same awakening a while back when changing industry. I was proud of my "API Design" that included header files, perhaps a python wrapper etc - whereas everyone else was talking about HTTP verbs, which luckily I was fairly well versed in.
- fidotron 2y ago> With the rise of IOS and Android, I expected the mobile devs would build something better than HTTP, without all the cruft from the past. But somehow that didn't happen. Google, in particular, early on went for the php developer audience. Frankly this destroyed the technical credibility of people in the mobile space and we have been living with it ever since.
- freetonik 2y agoHad a similar moment at one job. We were discussing possible API design choices for an integration project, and more than an hour into the meeting we realized half of the room was assuming HTTP. This rendered the majority of arguments spoken so far irrelevant.
- gollum999 2y ago> Suddenly, everyone was talking about HTTP APIs, when they said API. I had a junior dev try to correct me when I used "framework" and "API" outside of a web context. It caught me off guard at first, but the more I've thought about it, it seems inevitable as time goes on. The more abstractions we build, the more unreasonable it becomes to expect every developer to start with "bare metal" and work their way up. Schools are forced to teach with "the other side" (i.e. the highest-level abstractions) as the benchmark for graduating, because that's what employers need. So at some point they have to cut some of the more esoteric CS fundamentals and concepts to make room.
- hahn-kev 2y agoThey did that before, it all depends on your definition of bare metal. They probably don't teach assembly, or circuit design even though that used to be bare metal
- 01HNNWZ0MV43FF 2y agoI had another dev mix up "object" and "response" and say "JSON response" in reference to a request that sent JSON. I asked 2 or 3 times, "Response to _what_?" before figuring it out. That still lives in my head.
- layer8 2y agoFrom the point of view of the server, the request might be a response. ;)
- blackoil 2y agoBecause HTTP is ubiquitous and now performant enough. It has a whole ecosystem of battle tested tools that can handle any usecase you throw at it. So, unless you are writing an app used by billions of users or some game hyper-sensitive of latency or backend service for similar size platform, you'll do better with HTTP.
- alibarber 2y agoI think this comment misses what we're saying here in that there are many people working on things like operating systems, specialist desktop software and libraries, for whom API design has nothing to do with any form of network transport at all. In my case, the company I worked at shipped a product that came with a set of header files and dynamically linked libraries that exposed some of the core functionality to the customers for use in their own software, and designing this API was a specific task in itself.
- netsharc 2y agoAPI stands for "application programming interface". E.g. a graphics card driver can provide an API for an application (a web browser, a game, a calculator app) to draw an image on your screen... should it speak HTTP to do that?
- 01HNNWZ0MV43FF 2y agoOver the years I've come to like HTTP. It's mostly text-based, but you can send arbitrary binary data through it. The request-response pattern is a decent match for a world where most computers have no clue where they are, need help learning their own IP address, and are stuck behind trapdoor firewalls anyway, so the only really usable case is to reach out to a well-known server at a well-known address and ask it to do something. Of the whole web stack, HTML is the only part I've consistently hated since the big web revolution that started around 2007. It's just such a piece of shit. JS got faster and TS redeemed it substantially. HTML still sucks.
- icedchai 2y agoThe "big web revolution" started in the mid-90's. I think it started going down hill when JS and then CSS were thrown into the mix. That time (late 90's, early 2000's) would've been a good time to reassess if building "applications" on top of a document delivery system was really the right approach. Instead, we got workaround upon workaround, and now we have what we see today...
- quectophoton 2y agoThere's even "REST API", that now means "RPC over HTTP using JSON". I don't think I've ever seen anyone who describes their HTTP API as "REST" ever implement the HATEOAS part of the REST definition. And calling it REST without HATEOAS, is like calling a database ACID without Atomicity (for example).
- berkes 2y agoIs it really a disconnect? Or just a single poorly made game show? The article doesnt really get into this. It just describes the mistakes in a show, and hints at a few other anecdotes to then conclude there's a disconnect. I believe there may be such a disconnect (34 years of programming under the belt, here) but it's hardly more than a feeling, or belief. This article doesn't substantiate this.
- airstrike 2y ago> My growing feeling of disconnect gets fueled mostly by seemingly shifting notions. Some examples I've heard are people saying "vanilla JS" when talking about Node, or saying "JS without frameworks" when talking about React. The "woah" moment from the first paragraph is another example.
- simonw 2y agoIt's genuinely fascinating to me how many professional web developers these days - smart people who produce good work - don't know how to build interactive features using HTML on its own (and maybe don't even know it's possible). Being able to do things like this is really useful: <form action="https://simonwillison.net/search/" method="get"> <input type="text" name="q"> <input type="submit" value="Search"> </form> I've seen teams estimate a full day to add a link to a contact form because they need to refactor a bunch of React components to achieve that. I like being able to do this: <a href="/contact">Contact us</a>
- jetbalsa 2y agoI'm love old school HTML, need a autoscaling page, lets break out some FRAMESETs and some tables/iframes
- amelius 2y agoIt's because submitting a form interferes with all the other stuff running on the same page. E.g. after submission animations stop or disappear or skip a frame, annoying designers, etc. etc.
- moron4hire 2y agoI don't think there is really anything in your "etc. etc." I have never heard from any real user a complaint about animations stopping mid-flow. I think people know how pages work, in that I think they expect clicking things to do something disruptive, altering, changing. It's only been the design astronauts that have argued these discontinuities are "confusing" to users. If anything, sometimes I think they make the transition too smooth, to the point that it can be possible to miss it. Sharp changes are generally easy to notice.
- amelius 2y ago> I don't think there is really anything in your "etc. etc." "etc. etc." = anything with state, so this can be quite a lot actually ...
- 2y ago
- behnamoh 2y agoI really liked the font and found it, it's "IowanOldStyle": https://font.download/font/iowanoldst-bt https://font.download/font/iowanoldst-bt
- deleted 2y ago[deleted]
- cannibalXxx 2y ago[flagged]
- agentultra 2y agoThe Jblow and Muratori rants are contentious. Try arguing for formal methods some time. The industry has had enough time to expand to include many different zeitgeists. I find myself smirking when I read old ewd essays decrying how programmers then didn’t understand programming. Seems like we’ve continued down that path. From my part of the pond you’d expect the Computer Science questions to cover areas of combinatorics, abstract and linear algebra; satisfiability, search, and the like. But we are talking about a pop culture type of show and what is the most popular form of programming today?
- mattgibson 2y agoI wonder if every generation is doomed to feel this way. Socrates was horrified about the corrosive effect of reading upon young people's ability to memorise speeches. Plus ca change etc. https://www.perseus.tufts.edu/hopper/text?doc=Perseus%3Atext%3A1999.01.0174%3Atext%3DPhaedrus%3Apage%3D275#:~:text=For%20this%20invention%20will%20produce,their%20own%20memory%20within%20them https://www.perseus.tufts.edu/hopper/text?doc=Perseus%3Atext....
- commandlinefan 2y agoOn the other hand, as the guy on twitter recently said, "it's not fair that I spent my childhood teaching my parents to use a printer and as an old man I'm spending my old manhood teaching my adult children to use a printer".
- freetonik 2y agoTo be fair, it's not fair that printer manufacturers do this to us for decades.
- layer8 2y agoMy older relative is complaining that their working life roughly coincided with the time where computers became mainstream but were still hard to use, and now that computers have become easy to use (think smartphones and tablets) their (the relative’s) productive days are more or less over and all their hard-earned difficult computer knowledge is becoming obsolete. So they were the generation that had it hardest, because they had to deal with computers (unlike earlier generations) but had to do so before computers became easy to use (unlike later generations).
- iterance 2y agoTo some extent I'm sure the answer is yes, so I think the operative question is not "Are kids learning what I learned?" Instead it has to be something more subtle. Perhaps "Is kids' knowledge broadened and deepened by the media they consume?" more generally would do. It allows us to evaluate extent, change, and appropriateness more broadly. Not just the accessibility of a given topic, but how readily one can dive into the details and truly learn something. The landscape of media then can change, but this question does not react to any and every change in the landscape the way a nostalgic argument does. Socrates would have no reason to worry; a book can broaden and deepen knowledge, too. Are we?
- sesm 2y agoSo the programmer mentioned in the first sentence didn't know about 'preserve log' checkbox?
- MortyWaves 2y agoI’m guessing not which seems about right for someone that also doesn’t know about non-SPA web sites. Sad.
- oxidant 2y agoPreserve log is still helpful for SPAs when you want to compare requests across full app loads.
- 7bit 2y agoDid you read more than the first sentence? The answer is there.
- seanw444 2y agoThe level to which "kids these days" don't have to consider memory usage, cache locality, and clock cycles, is frustrating. But it is cool to realize how good our technology is now that most things aren't unbearably unusable, despite being designed horribly.
- kittikitti 2y agoIt doesn't matter if you're a kid, if you're not considering memory usage you were either trained by Google, became a developer through nepotism, or both.
- s5fs 2y agoIt’s also possible to work on projects, or in languages, or on systems where resource consumption isn’t a high concern. I wrote cobol for sun and hpux and these big old systems had plenty to go around. Important software comes in all shapes and sizes, as do their developers.
- icedchai 2y agoHardware giveth and software taketh away. My desktop today has 64 gigs memory, 12 cores. 10 years ago, it was 16 gigs, 4 cores. 20 years ago, it was 1 gigs, 1 core. 30 years ago, it was 16 megabytes, 1 core.
- listenallyall 2y agoIt cost me over $500 to upgrade my 4mb RAM to 16.
- sircastor 2y agoMy professional career has largely been web dev, where I haven’t really had to worry about resource constraints It was quite a lot of fun in my university final project to be developing on a 6502 (NES) in Assembly and find myself working in a very restrictive environment. Likewise, when I was working with a powerful microcontroller, but still only 2k of memory and 16k of flash and not being able to use some libraries I typically do. I was left having to reimplement stuff on my own for my own purposes.
- Swizec 2y agoAs a fellow 37 year old, I had a realization yesterday after a prolonged debate about HTMX vs React. For context: I’m a long time React fan, think htmx is neat, and remember all the reasons why HTML-over-Ajax didn’t catch on in the 2007 web development era. Been a primarily web guy since 2003 or so. The problem with React (and friends) isn’t React (and friends), it’s react developers. People who aren’t web developers first and react users second. I have interviewed (and worked with) so many frontend engineers with years of experience whose minds were completely blown by the idea of using a form submit event to handle form submission. Or my biggest pet peeve – button + onclick to change location.href instead of just making a link. Argh. So yeah I think we’re lucky to have grown up with this stuff and seen it evolve over time. Many folks these days come to the field backwards and miss a lot of the good stuff that’s available to them.
- edoceo 2y agoThe problem with X isn't X, it's the devs. I've heard that about PHP, JS, shell, .Net, VB6 and damn near every framework ever. But aren't we the devs? We're just in their code saying their baby ugly? There's gotta be a better way than just blaming noobs.
- Swizec 2y ago> There's gotta be a better way than just blaming noobs. Here’s an alternative read of what I said: It is amazing that these frameworks empower so many people to build working software that solves users’ problems and creates value. This is awesome! Sure the code sucks and we gripe about how many of the people don’t even care to learn the depths of the tech they use and clearly they don’t need to. This is a win. We can teach the ones who want to learn more and constrain those who don’t to where they can be effective without causing too much damage. And most babies are ugly. It’s fine.
- jzer0cool 2y agoLiked reading this, could you share a few examples. What you saw, what you wanted.
- juggernaut420 2y ago[dead]
- deleted 2y ago[deleted]
- rkozik1989 2y agoYou've noticed two things: 1. Every generation of programmers typically only has a certain window of knowledge, and everything before their time is simply foreign to them. Most developers aren't programming history buffs, they don't read books from the past to learn about technologies or how they work, how we got to now, etc. 2. When you're starting off on your journey as a programmer you're using a lot of things without understanding their implementation, and that understanding for most individuals whom I've worked with comes from having to debug issues.
- commandlinefan 2y ago> Every generation of programmers typically only has a certain window of knowledge That's true, of course, but I think the disconnect he's pointing out is: a) deeper than that and b) new. I grew up a ways before he did and my first serious computer was a commodore 64. Like his 286, there was nothing you could do with it _except_ program it, and programming was hyper accessible. I immediately understood C's pointer syntax when I first came across it because the only way to show graphics on a C64 is to write to a specific memory address and the only way to intercept keypresses is to read from one. Fast forward to the 21st century. My son is a smart kid - graduated valedictorian of a competitive high school - but he grew up with "computers" that hid the programming interface down so far that most of his experience with actual programming has been through emulators so the whole thing feels (and is!) artificial. He still struggles differentiating between what's "real" and what's emulated and I can tell from interacting with other programmers his age that he's not alone.
- simpaticoder 2y agoThe GP's point is more general and stands. Technologists inevitably start off "in the middle" of a stack of technologies, and then choose to dig down and/or build up from there. It is inevitable that newcomers will not understand the technologies upon which their current work rests. A certain fraction of those will become fascinated and drawn to understand the underpinnings of their work, for an edge, or for the love of it, or both. This process happens more naturally over time if you grow with the technology. For example, if you started programming with HTML in 1995 you not only have ~30 years of experience, but you've also seen the changes as they occurred, and have a great deal of context about the how and why each of them happened. That kind of experience can only happen in real-time, unless some kind soul is willing to write a manual to help newcomers speed-run it. Such a manual is often called a "textbook".
- commandlinefan 2y agoI often help younger developers with problems that involve absolute vs. relative paths - their code doesn't work because they're invoking it with the wrong working directory. It's immediately obvious to me because I grew up using the command line, where files and paths are elemental. They're usually _really_ interested in properly understanding what's actually happened here, but they've been so intentionally shielded from the fundamentals of files and directories that they need quite a bit of time to let it all sink in. The solution, of course, is to teach things bottom up, but I have some sympathy for beginners who lose patience with spending so much time dealing with something that doesn't even _look_ like a computer from their perspective.
- moribvndvs 2y agoIt has been very eye opening watching young and brilliant programmers who have grown up with mobile devices struggle when it comes to traditional environments. Many struggle with things that seem basic, like file systems, processes, memory management, how to use desktops and even mice, etc. However, once you solve or abstract away those things, many are able to churn out complex software at an impressive rate, particularly when they are able to assemble tool chains and frameworks together like legos. Then they go back to the struggle bus when something in that chain fails or functions unexpectedly. Differences in the types of environments and how they interact with them between age groups makes sense in a pretty boring sort of way, and at any rate is solvable through simple experience. It’s more interesting to me that this observation is another point of correlation in the notion that the industry has aligned itself with productivity over any other metric. While productivity is important, this unbalanced favor has introduced fragility and unsustainability into the industry and end user market.
- reaperman 2y agoSo much of the modern computing environment goes incredibly far out of its own way to hide information from the user. It's getting difficult just to see the URL in mobile browsers, and in some fairly general-purpose computing environment (iPads, etc) the concept of a "filesystem" has become very abstract and increasingly difficult to ascertain. It doesn't surprise me that people half my age have difficulty with some of these - it's much harder for them to play with and explore the concepts.
- recursivedoubts 2y agoThe blame falls on us olds for not communicating the benefits of the hypermedia approach to the younger generation, and allowing flashy front end boosters to bully us into silence on the topic. The tide is turning to an extent though. Here is my contribution: https://hypermedia.systems https://hypermedia.systems
- FireSquid2006 2y agoLove this book!
- codazoda 2y agoI’ve been feeling this same way but didn’t want to articulate it, possibly out of fear. I also wrote a little book based on “old school” or “pure JavaScript”. I’m sure you could make some of the same criticisms of that, but I tried to make it pure and down to the basics. It’s on Amazon at the URL below but if you’re willing to give feedback, reach out and I’ll send a free copy. https://a.co/d/bwF4YF5 https://a.co/d/bwF4YF5
- btreecat 2y agoHey great work!
- jillesvangurp 2y agoIt's not so much a disconnect as more of a reluctance to specialize in what is an increasingly legacy/archaic way to build applications. I studied in the nineties and I've seen it all. Server side model view controller style UIs where each click results in a completely new page being fetched that is completely static slowly died over the last two decades plus (ever since MS pioneered XmlHttpRequest and AJAX became a thing in 2001). Not doing requests via javascript still works. And for quick and dirty stuff where you don't care about how things look and feel it's a perfectly valid way of doing things. A lot of developer tools fall in that bucket. And a lot of developers are in any case a bit challenged on the UX front anyway so there's a good argument for not using too many ways to shoot at your feet. But having every request wiping the current page, scrolling to the top, etc. can be a bit jarring as a UX as well. And there's the whole round trip latency for fetching pages too, which can be noticeable. In other words, if paying customers are involved you probably should not go there. Mostly people expect things to look and feel nice and have some designers involved with the whole thing. End users don't care about any of this of course. They also don't care if the app is native, a webapp, or something you could have hosted on geocities 25 years ago. But they do notice if things look dated, crap, or otherwise a bit meh. They especially don't care how things look under the hood. The whole notion of semantically pure HTML, vue vs. react, and all the other nonsense web developers obsess about. It does not matter to them at all. You could use divs for every freaking HTML element and they couldn't care less. Or render the whole thing with some native UI toolkit to a canvas (which is an option these days). As long as it does the job. You don't have to do a SPA. But you kind of do have to deliver something that works and looks and feels nice. With WASM, we are kind of getting a lot more ways to do things. The whole game of working around browser quirks and limitations with dom trees, CSS, and what not is not necessarily the way of the future.
- MatejKafka 2y agoMy personal issue with SPAs is that the experience is often not really better than the old school way, it's just the the issues and failure modes are different. SPAs tend to be slower to load, break platform conventions by re-implementing browser behavior and they're are more stateful, making invalid states harder to recover from. Personally, unless the interactivity is needed (i.e. web apps, not web pages), I prefer a more basic site where I can be reasonably sure that UI will work the same way as everywhere else, even if it's not as fluid.
- openrisk 2y agoPeople talk about software "technologies" and it is true, there is some technology underlying them, but its mostly economics. The nature of software with its multiple abstraction layers means that when the economics is "right" you can pretty much transmogrify anything into anything. E.g., you can setup a JS-based web server as a classic web framework serving good old html and thats not a joke, its reality. Is web software economics today any different than it was in the past? You bet it is.
- memtet 2y ago[dead]
- deleted 2y ago[deleted]
- relaxing 2y ago> Which method removes and returns the last element of an array? The answer is “pop”, right? I think that’s a fairly generic data structures question (if you treat the word array as a standin for any modern iterable collection type.)
- layer8 2y agoStacks in computer science aren’t random-access data structures, which arrays are. Conversely, arrays in computer science are by default thought of as having a fixed size, and don’t inherently have a dynamic size variable associated with them that would be necessary for a pop operation. You can implement a stack on top of an array, but that doesn’t mean that they are the same data structure. The array would be an implementation detail of the stack. (Alternatively, a stack can be implemented as a linked list.)
- relaxing 2y ago40 years ago that would have been true, but meaning has since shifted. Hence the last statement in my response, which you ignored.
- layer8 2y agoThat's the usage in JavaScript, but there has been no general shift. What I wrote is true in Java, Go, Rust, and Python, for example. In theoretical computer science, it is certainly the default assumption when the word "array" is used without qualification. See also https://en.wikiversity.org/wiki/Data_Structures_and_Algorithms/Arrays,_Lists_and_Vectors https://en.wikiversity.org/wiki/Data_Structures_and_Algorith... Or see the use of arrays in "Introduction to Algorithms", one of the standard textbooks about algorithms and data structures, the current edition being from 2022. There is no notion of arrays being resizable there.
- rafram 2y agoBut not PHP (where an array is actually a dictionary, too...), Perl, Swift, or most scientific languages like Matlab and R. C-influenced languages usually differentiate between "arrays" and "lists"/"vectors", but that's just convention. Java, of course, calls its standard general-purpose list implementation both "array" and "list."
- shahzaibmushtaq 2y agoA growing disconnect begins to grow when coders learn from bootcamp/courses that web development is an ocean, and this ocean is as big as the well. Strong fundamentals are essential in every field, otherwise the disconnect will continue to grow and no one can do a thing about it.
- purple-leafy 2y agoI’m a new developer (2-4 years experience, all self taught) and I get what they are saying. I obviously have gaps in my knowledge (started with Python, moved to frontend). Frontend is too abstracted from actual CS. But I actively take University papers in my spare time on CS, and do C in my spare time to appreciate the lack of abstraction in low level code. I really enjoy this (learning and C) more than economic programming (frontend, web, career). I just love learning and realising how little I know. The latest thing I’ve learnt is that structs can have holes, and struct packing for situations where you need specific address offsets. Made my own bitmaps from scratch etc. Next I’m thinking of picking up a Lisp.
- JohnMakin 2y agoI think people just focus on problems entirely within their own domain and rarely branch out to anything else. The amount of times I've had to explain to senior devs of 20+ years how DNS works at a very simple level would astound you, which is something that I would assume should be picked up if not by learning, through sheer osmosis, but you'd be surprised. If you lack a formal education, and maybe went through a bootcamp - which there's nothing wrong with - you may not know a lot of things that would surprise this author.
- deleted 2y ago[deleted]
- scotty79 2y agoSomebody at some point was predicting that JS is going to eat software world. Even made a funny talk about it. It's gradually happening.
- reshlo 2y agoAre you thinking of this? https://www.destroyallsoftware.com/talks/the-birth-and-death-of-javascript https://www.destroyallsoftware.com/talks/the-birth-and-death...
- graypegg 2y agoI would really like to try writing something along the lines of “the web from scratch” one day. I wouldn’t want it to be just a retelling of the history of the internet, but rather building up a set of abstractions from some physical example of communication to your own mental model of a hypertext standard on top of a simple transport protocol, sort of like Charles Petzold’s Code. The web is complex nowadays, but it also actively hides its implementation from you to be a better product. Dialing a phone number with a modem on both ends has a sort of real tactility to it that’s pretty alien to young people that expect it to be “harder”. You can pick up the phone on the line and hear that something is going on. The computers are “talking” on the phone. A metered Internet connection means I was constantly aware of how much data is going over that phone call. What takes huge chunks of that budget and what barely touches it. My ISP even gave our family some web space to use. Like just the peek behind the curtain you get from putting a file on an FTP server, then requesting it in telnet and seeing every letter I typed zip in from the other side really illuminates a lot. If I ask the computer I called for a file in a special way, it sort of shouts it back at me over the phone call, and my computer can listen and understand that. It’s not like it was the best implementation of the “product” that is the Internet. Anyone saying the contrary really is an old person shouting at a cloud. But I do have some sense of being lucky to get to explore the web in that era!
- pimlottc 2y agoAm I the only one that gets annoyed by that "enhanced representation"? All I want to see in my editor window is the code itself. Every year, VS Code goes further and further in adding more inline hints, error messages, test results, stacktraces... It starts getting confusing, distinguishing the actual sources from the other stuff.
- quectophoton 2y agoUgh. Maybe not exactly what you're talking about, but whenever I have to use a mainstream IDE for one reason or another, or some web REPL (e.g. to share code snippets), I end up frustrated but also really curious about how other people program. * I type, then press enter, but a suggestion appeared in between so my enter got turned into "accept suggestion" instead. Or same with pressing an arrow and instead of moving my cursor it now selects a different suggestion because I pressed the arrow 10ms too late. * I type a character like `"` or `<` or `[` or `(` or stuff like that, and it gets paired automatically. Or I type `]` or `)` and it does nothing because it's the same as the character under my cursor and it "helpfully" moves the cursor to the right instead of inserting the character (e.g. I want `]]` or `))` but it just ignores me and it leaves `]` or `)`). Worse is when this happens inconsistently, like pressing a `"` character being a 1d3 roll on the result (if my cursor is currently on `"`, then will I get `""` or `"` or `"""`?). * I'm going to move the mouse to select some specific part of the code, but when I'm going to click it inserts some garbage right where I was going to click (e.g. type hints, some information about how many references are there, stuff like that). I never want anything to move my code around. * (Other similar stuff I'm sure I'm forgetting.) I'm not saying things like those aren't useful, but those defaults are so different from what I want that they're more of an inconvenience for me and I have to spend the first hour changing them (but I can't do this when physically pair programming). Otherwise it's basically impossible for me to develop muscle memory at all, because I have to constantly guess what's going to happen and what's going to move or appear or disappear. TL;DR: Mainstream IDEs defaults are frustrating for me when I try to go keyboard-only, and also when I use mouse for some actions.
- vrnvu 2y agoI often see engineers from other teams ask for a "non-blocking endpoint" because they don’t want to block while waiting for a response from the server. What is a "non-blocking endpoint"? If you are making the request, just do not block...
- lildata 2y agoIt is funny that "the Web" as a platform has become like the mainframe for banks and some big companies. It is an ubiquitous legacy, a critical infrastructure of our societies and a spaghetti that cost everybody a lot. In the end it is controlled by the biggest corporations and various interests. Very hard to disrupt and replace.
- darepublic 2y ago> I've always felt safety in coding. It was a comfortably logical, deterministic, and beautifully consistent refuge from the world of vague and ambagious reality. I also felt certain kinship to other programmers, it was my tribe. So I'm worried about this feeling of disconnect, a little bit. This passage resonated with me. At a recent contract I saw some PRs from my team mates that I found baffling. But rather than comment on it or intervene for once I told myself to just ignore it. It's Chinatown, or something like that