8 ms·
I hereby pardon all junior engineers
- zubairq 3y agoInstead of complaining about others why don’t you build something great yourself?
- surprisetalk 3y agoAuthor here! Totally agree. I'm secretly off in the wilderness trying to build something I think will be great: [1] https://scrapscript.org https://scrapscript.org In the meantime, I thought some concrete complaints could inspire people to work together :)
- deleted 3y ago[deleted]
- zubairq 3y agoSome nice things in the language, well done! I used content addressable code snippets stored in IPFS for my own system too. Content addressable code seemed to start with Unison, but now a lot of new programming languages are seeing the benefits of this technique!
- tacone 3y agoLooks great, any sample app out there?
- surprisetalk 3y agoNothing yet! Some folks from the community just stepped in to help me and we're now making incredible progress together. At this pace, I'm expecting a very rough first release in January.
- throwawaaarrgh 3y ago> It seems like nobody knows how to build things anymore. The Chinese, Japanese, Koreans, Germans, etc might disagree. There's a lot of people out there who seem to be able to build very high quality things fairly quickly. It seems like it's the Americans that are struggling. We have for a long time, actually. I would argue we just have a shitty building culture. We chase trends, cheap out on materials and salaries, overcharge for services, ignore maintenance, and shun process. We're way more interested in the shiny and shooting by the hip than the boring careful measurement. Growth is more important than quality to us. Greed and the new are our gods. HN is the pulpit. Laziness is the ladder on which we climb toward the heavens, ignorance our fuel. Watch this, I'm going to reinvent the wheel! We won't be able to roll on it but we can sell it for a bundle before it collapses. It doesn't seem this way because we have so much money keeping us afloat. Like Google, the company renowned for its tech culture, but really makes most of its money selling eyeballs to Nike and Kraft.
- wewtyflakes 3y agoIt has been my experience that there are good and bad engineers from all origins; Americans do not have a monopoly on it in either direction, nor does anyone else.
- ttoinou 3y agoIf you can't generalize then you can't think. Of course any affirmation can be turned down on the basis that it is not specific enough. OP is pointing at differences in cultures, they do exist.
- wewtyflakes 3y agoIt sounded like the person I was responding to just wanted a lazy poo-poo soundbite. There are many examples of all of the countries mentioned making ridiculous/awful products and also amazing products.
- alex_lav 3y ago> If you can't generalize then you can't think If you blindly follow others' generalizations without question, you can't think.
- xrd 3y agoTaylor was one of my favorite people at strange loop this year. His outfits were fantastic. I love his blog even more. And he's a courageous and deep thinker.
- surprisetalk 3y agoAww what kind words! Come stay at our place if you're ever in the Southern California area :) If you want to copy my outfits, I find all of my strange clothes at Anime Expo every July! I just purchased an egg sweater from a vendor I found there: https://shop.kinwamonster.com/products/cardigan-egg https://shop.kinwamonster.com/products/cardigan-egg
- xrd 3y agoThat would be great! I hope to do that someday. I'm trying to take my daughters to Japan in March. Let me know if you need anything direct from the source!
- imchillyb 3y ago> How fast should programs boot? How long should it take to make bug-free software? How long should a smartphone stay relevant? How much mining should it take to live? How many steps should it take to get to my local grocery store? None of this is really relevant. None of these questions 'need' answers. What do the customers need? Where is the market for my goods/services? These questions are relevant. People know and love to build things. The things they build and invent are then taken over by middle managers, project managers, high level executives, and politicians. It's not the builders or makers that can't build things, it's the budget constraints, board-room death spirals, and project management to death that makes projects hot-garbage. We can't build things because they won't let us. We show the powers that be a 7 course meal, and they make it a McRibb. Sure it's tasty, but it sure ain't what we wanted to build...
- Mistletoe 3y ago[flagged]
- jhp123 3y agoI connected with this, I've had many of the same thoughts lately. It's a thoughtful essay and I have no idea why it's been flagged? > When fewer than 5,000 programmers existed, they built Lisp (1960) and APL (1966) and sketchpad (1963). With over 5 million programmers today, the best we can do is Rust and React. It feels like this has worsened even just in the last 15 years. When I started in the industry (2008ish) it felt like there was a lot of experimentation and new ideas compared to today. Memes like "language wars" and "javascript framework of the week" come from the recent past when there was not the same monoculture of like 3 big JS frameworks, 5 big languages, etc
- 000ooo000 3y agoIt has a distinctively LinkedIn style of writing, e.g. many one-sentence paragraphs. Could be why.
- rramadass 3y ago> It feels like this has worsened even just in the last 15 years. It is a question of Statistics/Probability and similar to statements like "The End of Science"(see John Morgan's book) i.e. all the main/major aspects of knowledge are already known. IMO the following are the reasons; 1) In the early days the field was populated with experts and the quality of the output was high. There was also a lot of unknowns to be mapped out and hence the quality and importance of inventions/discoveries were startling. 2) Once you have the fundamentals of a Scientific Theory with Principles and Guidelines laid out for a particular field almost all future developments in applications can be anticipated and will seem like "nothing new". Our very advances in Mathematics and Sciences negate future novelty. One good example is the current advances in AI/ML which is merely a hodge-podge of Statistical techniques/Computation models and lots of power. 3) With the rise of the Internet/other forms of content delivery, a very large number of non-experts now have access to a bullhorn to spread noise and amplify it in very many dimensions in the service of vested interests like business/power/money/etc. Hence the s/n ratio is very much diluted i.e. there is now a lot of junk to wade through. 4) Finally; Social mores, norms and values are very different today and hence discovering/inventing Knowledge has been made subservient to other goals/needs.
- williamcotton 3y agoI don’t blame the junior engineers either. I blame their seniors and managers. Leadership is especially awful these days and across most industries. Leaders tend to be too far removed from object level reality and just sit around blowing smoke up buttholes all day long. If you got laid off in the last year or two it’s because your leaders failed you with their shitty cargo cult approach to running a business. “Der, Google is hiring like crazy and dey lots of money and I want big big boat… so what if we hire like crazy and make radios out of coconuts?” It’s easy to throw shade but when I was last at the Facebook HQ I saw Mark Zuckerberg down on the floor talking to a young designer. He also took personal responsibility for the slimy layer of middle management that emerged over the decade prior, the result of which contributed heavily to the need for layoffs in the first place.
- rramadass 3y ago> I don’t blame the junior engineers either. I blame their seniors and managers. Leadership is especially awful these days and across most industries. Leaders tend to be too far removed from object level reality and just sit around blowing smoke up buttholes all day long. 100% agree with this. "Modern Management" as practiced today is a major factor in the decline of quality creativity/research/engineering.
- PlatinumBench 3y agoI liked this post, especially this quote: > The norm is to battle software rot and add features ad infinitum. Software engineering is so expansive, it is ideas built on ideas built on ideas. I learned Node.js in my free time because of the derision that is rampant for FE engineers. Node.js is built on C++, which compiles down to machine code which runs on a CPU that has it's own firmware. My Node.js application sits in a docker container on a Linux server written in C that somehow knows how to accept network requests and respond with data to a user's browser, using protocols and methods that were conceived of before I was born. The application got on the server because of my gitlab pipeline that first built my application and bundled it with Webpack, then ran unit tests with Jest, then ran e2e tests with selenium, then runs a bash script to git clone my code to build a docker image. This all to change a response header from a 200 to a 203 to align with best practices. At any given day I am working on 30 levels of abstraction, trying to deal with elitists who were around when the internet was in its' "glory days" telling me now that the stuff I am working on means nothing when compared to the pristine web we had in 1987 when a gif of a dancing baby blew people's minds. Now the internet is layers upon layers of protocols and languages and code and tracking that if I take time to look back on and learn, the industry will have moved past me to Next or Nuxt or Nyxt or Naxt or whatever bullshit flavor of the month library I am required to master and have 3 years of experience in (it came out a month ago). There is no extra space for regular people like me, we can't build things any more; at least not things of note, things that get used. And while building something that never gets used is great for your portfolio, it feels like making a painting and immediately sticking it in a safe. What is the value if no one even sees it? > When fewer than 5,000 programmers existed, they built Lisp (1960) and APL (1966) and sketchpad (1963). With over 5 million programmers today, the best we can do is Rust and React. Being a standout of 5000 people is extremely hard, being a standout in 5 million is a statistical anomaly even with specialization. And people do it in the same sense that people win the lottery: someone has to but your chance may as well be zero[1]. 1. https://en.wikipedia.org/wiki/Lottery_paradox https://en.wikipedia.org/wiki/Lottery_paradox
- gymbeaux 3y agoThis article touches on A LOT. I would say the focus is on why software projects are so large and complex. I think about Fallout 4, a remarkably buggy and inefficient piece of software; I think about the React + Redux web app that a previous employer sank millions of dollars into to succeed a perfectly functional, perfectly adequate C# MVC WebForms app; I think about how it seems today’s software engineers are valued not by what they built but by what they know. 1. Fallout 4, a game released by the notorious (for bugs) Bethesda Softworks in 2015. Despite the ample bugs, some of which were ignored by Bethesda and ultimately fixed by an unofficial, third-party patch, it won Game of the Year in 2016 from BAFTA. In 2015 I lacked the hardware required to run this game above 30 FPS. Today, I have a $2,000 monitor and a $1,000 graphics card, buuuuut Fallout 4 doesn’t recognize newer graphics cards and defaults the quality to “Low” with the lowest resolution possible. Additionally, it doesn’t support ultrawide monitors as many games these days do. Finally, it crashes every couple of minutes. I’m not sure why. It’s not a mod causing it. I’m using a normal aspect-ratio monitor now. So this game, not even 10 years old, has been abandoned by Bethesda. Like Fallout 3 before it, I’ll probably have to install a litany of unofficial patches and make edits to config files to get this game to run the way it should out of the box. 2. SS&C’s, Advent Software’s, Black Diamond’s “BD3.” The amount of effort that went into the UI was, to me, obscene. Probably 40 devs working on this. We had a Storybook as a style guide. We had internal tools (also in React and using Redux for… some reason). The web app looked beautiful, BUT always had bugs. Always. An area of the site would be enhanced, and then there’d be some bugs. I once spent about a week working through a bug that only happened on mobile Safari, and the CSS fix was ultimately hacky. To debug this, I had to have a Mac connected to an iPad, and use Safari’s debug tools to connect to the Safari on the iPad. I remember it didn’t “just work”. All this effort to make a web app whose primary purpose was to look good. I think the main concern was keeping up with the competition. Evidently custodians like BlackRock bounce around wealth management platforms and we were directed to cater to every whim of the large clients. If they wanted some bullshit little toggle on the benchmarking page to show grid lines, one of our dev teams would inevitably spend hundreds of man-hours making it happen. If they didn’t, we might lose BlackRock, which would be worse than spending $100,000 on adding grid lines to a chart. 3. I have actual, useful code on Github. I have a catalog of Medium articles I’ve written on subjects like ETL, AWS and Azure. My StackOverflow is in the top 5% this year for rep received. All of that means fuck all to any employer if they are looking for someone who is familiar with DataBricks and I’ve only used Spark and AWS Glue (for example). I get it, most people’s Github profiles are in a sad state… but wouldn’t you rather hire someone who clearly knows what they’re doing, than someone who say solves your Leetcode in O(log(N)) time?