I’m learning swing dancing. It’s been humbling. It’s humbling because all my life, I’ve been really good at technology - I specialize in biotechnology and manipulating DNA, but am also fluent in programming (mainly python, go, lua) and am able to build hardware - even helped run a robotics startup for a while. Anything related to technology and science comes easily and naturally to me. This isn’t to brag, but just a…
I tried to learn to dance (hated it). It is a bit of a weird thing though, there as social events where people feel like it is OK to really try and pressure people into dancing. It is really annoying.
Ask HN: What was your most humbling learning moment?
391–400 of 704 posts
Re: Ask HN: What was your most humbling learning moment?
#392For the first class, I had prepared a bit of an overview, starting with the perceptron, and then showed Minksy and Papert's proof that it could only learn a linearly separable membership function. So I had these formulas on the blackboard, ending with something like "for every delta > 0 there's an epsilon such that ..." etc. Then before the break, I ask if anybody has questions. One person raises their hand and says: What's a vector?
That was a bit of shock. I had completely not understood the knowledge level of my students. Not that I ever became a good teacher, but that was an eye-opener.
Re: Ask HN: What was your most humbling learning moment?
#393Earlier quoted context omitted.
I call myself an engineer- but the way I understand it is that I still have to know when to use a hammer like simply copy paste code and not some complex solution.
The problem in software is that very frequently you dont have a real hammer. You have hundred amalgamations of swiss army knives that do everything. Like what is the hammer when you want to add some nice dynamic content to a website? Is it just javascript or maybe react?, Angular?, Svelte? Or another example: you want to code a command line app, what language is a hammer here?: C++?, Go?, Bash?, Python? This analogy…
Most of the time however stakeholders will prefer that someone unleash the last technical shiny tech stack (that no one master in the team and that is about to be dethroned by the even newest thing) to deliver a pixel perfect reproduction of the mock-up rather than question the relevance of the proposal.
Re: Ask HN: What was your most humbling learning moment?
#394Only a few years back did I fully realize pickles and cucumbers are the same vegetable.
Re: Ask HN: What was your most humbling learning moment?
#395Re: Ask HN: What was your most humbling learning moment?
#396Earlier quoted context omitted.
As a good friend of mine often says: We work in a field of people who envision themselves as artists, when all that is wanted are painters.
No one wants to be a "programmer." They'd rather be called "engineers." With none of the licensure, mandatory education, and so forth. But the world needs programmers and technicians for most of the work we have to do. I do comparably little "engineering" and the little I have done that qualifies for such a statement I recall. Majority of the work is programming and technician work. Nothing wrong with that.
Engineers shouldn't compromise on things like safety, security, legislation, budget, properly documenting, properly communicating with others, etc. Same as anyone working professionally with code should, no matter the title.
But there's nothing that says that engineers should only be doing groundbreaking or interesting work.
The "artist" analogy works much better.
EDIT: Perhaps the main difference is what psychoslave mentions below – engineers are expected to question the relevance and necessity of requirements, and work together with business, rather than just doing as asked.
Re: Ask HN: What was your most humbling learning moment?
#397For my part: I think I learnt at age 35 the difference between sneezing and coughing. Duh!
Re: Ask HN: What was your most humbling learning moment?
#398Learning that some folks can produce so much value with crappy code. I've seen entire teams burn so much money by overcomplicating projects. Bikesheding about how to implement DDD, Hexagonal Architecture, design patterns, complex queues that would maybe one day be required if the company scaled 1000x, unnecessary eventual consistency that required so much machinery and man hours to keep data integrity under control.…
Re: Ask HN: What was your most humbling learning moment?
#399When I was younger, I had an issue with external vs internal validation. Sadly, it heavily skewed towards external validation. I was on the chunkier side for a lot of my childhood and into high school. Joined wrestling and stayed with it. Lot the weight, grew, and gained muscle. Also started to get a lot of attention from the opposite sex. That, with the external validation issue, leaned into it and just had fun. It…
A thought I have had in the past also, I think it is very true.
Re: Ask HN: What was your most humbling learning moment?
#400Earlier quoted context omitted.
It's cliche, but I really do feel reading the Art of Unix Programming gave me a very good sense early on for how to walk this line carefully. Unix programs are high quality - but they're also, ideally, small , and written with an eye to compositionality with the rest of the ecosystem. The best architecture is in the middle, and often the best first draft is a simple series of pipes. https://www.catb.org/~esr/writings…
(Honest question) What is the difference between this microservice architecture that gets a lot of hate here?
Unix utilities are stand alone and used as needed for specific tasks. They hardly change much, have no data persistence, usually no config persistence other than runtime params, and don't know about or call each other directly.
Microservices are moving parts in a complex evolving machine with a higher purpose that can and do affect each other.