181–190 of 211 posts
Thanks for being around everyone.
I used to tell my father about communities that build them around a particular coffee shop with tables that have different kind of conversations ..
YC conversations are the best ( least fluff, more stuff) There is no garden without a gardener.
Thank you @dang and @tomhow .. ( before this post I had no clue who you were so thanks to @prodigycorp as well )
Truly grateful to everyone in this community.
I discovered the world around Ruby on Rails, then the modern JavaScript ecosystem (and CoffeeScript followed later by TypeScript), burned out, focused on Ruby, added Rust to my toolbox, wrote a small hobby operating system that had to have its own Lisp dialect of course. I was inspired to create so many side projects over the years, most of them open source, thanks to the influence of this community.
I also tried my hands at starting a startup obviously, multiple times, but I'm a solo dev and didn't succeed at finding a profitable niche for myself, instead I applied my knowledge to better understand the business and product sides of the startups I've been working for which made me a better engineer for sure.
This community almost made me move to the Silicon Valley, but instead I traveled the world as a digital nomad when everyone was doing it, and came back home to settle down in a forest close to my roots.
Reading you all daily I can imagine what could have been my life at the heart of the tech world, and at the same time I'm happy to read its pulse from afar.
I hope HN will still be here in 15 more years, thanks everyone!
I still get value. But there's too much noise I think. I also think I'm older now and I'm more adverse to "done it, seen it"
The odd "made an app to do basic thing xyz" doesn't get my attention anymore.
Also, posts related to science get a hard scrutiny. Most posts are just cross references to poorly moderated subreddits. That, or they're just posts directly from archx with no external paper references. I'm not a scientist, but I know enough to know when to ignore bullshit.
Most posts to HN are still mostly bullshit. But I know enough to occasionally see something interesting. That's may be 4 times a year at this point.
...
I also want to add more context. I've been in the Anathem ideology for about 20 years now. It has shaped my world view. Call me fra geuis.
If you want to present what you think are new ideas, be prepared to back them up. When we get the Loreites up and running, I'll refer you to them.
Thanks HN! I regularly open HN during lectures. There is no better way to show my students what software engineering entails and why I focus on certain topics. Is SCRUM really as great as its evangelists claim? Let's read HN comments. What are good use cases for UML? Let's check out HN. Does anyone actually care about CoCoMo or CMMI? Let's read ... oh - nearly nobody's talking about it there. Maybe it won't be that r…
>What are good use cases for UML? Let's check out HN. Are there good cases for UML outside the raison d'être of middle managers circa 2007?
- In a nutshell: everyone should know about UML and how some relevant diagram types look. Nobody should use it religiously.
- Diagrams are great tools for communicating ideas and implementations on an abstract level, and for interactively thinking about ideas that can be drawn in some way. A diagram can also visually highlight problem areas (e.g., components with many dependencies).
- Good use cases for diagrams in SE are e.g., explaining high-level architecture to someone, thinking about and refining database schemas, documenting interaction flows, or giving an overview of class structure in automatically generated code documentation
- It is nice to have visual consistency - it makes parsing a diagram so much faster and less error-prone. UML provides sensible guidelines or inspiration on how to draw e.g., a sequence diagram or a class diagram. There is no need to re-invent the wheel.
- In most cases, knowing about the diagram types and their approximate design is enough. As probably very few people know what the different styles of arrows or boxes might mean, it is a good idea to annotate important elements with their meaning.
- For thinking/communication, drawing diagrams by hand is the best way. Excalidraw/tldraw are nice for stuff that should go into static documents.
- Documenting the state of a system with manually generated diagrams is tedious and requires constant updates. A better way is to auto-generate e.g., class diagrams using PlantUML or Mermaid.
- Nobody uses UML for designing complex systems and then auto-generating code.
Been here 18 years. Almost never comment, but I come back everyday for the insightful comments. Thank you @dang for the great moderation and thank you to great HN community.