Live data from Hacker News

Challenging projects every programmer should try (2019)

austinhenley.com

91–100 of 346 posts

Re: Challenging projects every programmer should try (2019)

#91

I wish every dev would try projects and things completely unrelated to computers. I enjoy being outside. These headlines “projects every dev should try” really annoy me. I try to put in enough effort at work, and that’s tough. But I have been messing with computers for over 20 years now.

A strange sentiment for someone who's wasting time heckling articles on HN.

Of course nobody said don't go outside or pursue non tech interests.

Re: Challenging projects every programmer should try (2019)

#92
post #65
post #24

While writing a text editor, a compiler, an operating system, or a raytracer might make you a better programmer, it won't make you a better software engineer. In fact, it might make you worse at software engineering, because it embodies the disastrous "Not Invented Here" doctrine. Hackers like to obsess about Big-O, data structures, HoTT, and other high-theory stuff, yet the following skills, essential for software e…

Gentlemen, you can't hack in here; this is Hacker News.

I'm shocked, SHOCKED, to find that hacking is going on in here!

Re: Challenging projects every programmer should try (2019)

#93
post #73
post #62

Earlier quoted context omitted.

And the most challenging part is making a text editor that actually works well from a usability perspective. Which has almost nothing to do with data structures and optimization. I've used dozens of text editors. I have never once thought "man, that thing is slow". But I have thought "man, that thing is a bug-ridden, unintuitive piece of garbage" many, many times.

You must not have used Eclipse back in the day

or Atom

Re: Challenging projects every programmer should try (2019)

#94
post #24

While writing a text editor, a compiler, an operating system, or a raytracer might make you a better programmer, it won't make you a better software engineer. In fact, it might make you worse at software engineering, because it embodies the disastrous "Not Invented Here" doctrine. Hackers like to obsess about Big-O, data structures, HoTT, and other high-theory stuff, yet the following skills, essential for software e…

What if we don't want to be "software engineers"? I'm still not totally convinced that "software engineer" is even a thing , frankly.

I honestly don't see a difference between programmer and software engineer. The one I see a difference with is "coder"

Re: Challenging projects every programmer should try (2019)

#95
post #24

While writing a text editor, a compiler, an operating system, or a raytracer might make you a better programmer, it won't make you a better software engineer. In fact, it might make you worse at software engineering, because it embodies the disastrous "Not Invented Here" doctrine. Hackers like to obsess about Big-O, data structures, HoTT, and other high-theory stuff, yet the following skills, essential for software e…

> In that spirit, I offer the following alternative challenge: Create a web search engine.

Yea, no thanks.

If I'm going to work on something in my spare time, I am going to work on something that I am interested in and find fun. I generally loathe the dirty work often involved in software engineering and debugging all of these dependencies all the time. It's exhausting. Doing things from scratch puts me in charge.

And I mean, creating a search engine is the ultimate "not invented here" project. I'd just pay for and use Google, Bing, or whatever else API to do things for me. So it doesn't even make sense in the context of your objections.

Re: Challenging projects every programmer should try (2019)

#96

Earlier quoted context omitted.

[flagged]

I genuinely love your sentiment. We have way too much faux asceticism and way too little self-mockery in this godforsaken industry that pays us all way too much money. Programming is wizardry. But being a professional one (a software engineer) is a ridiculous occupation we're coerced into. We all know this, otherwise Silicon Valley wouldn't have been a universally cathartic show. But GP is completely correct that all…

> But GP is completely correct that all of the fun, magical projects in the OP article are antithetical to the profession.

I guess I was emphasizing GP's point. The profession is the problem. Not the subject matter. I love computers.

Re: Challenging projects every programmer should try (2019)

#98
post #32

I would really love to try my hands on something much more physical, like a robot; or a drone with autopilot; maybe accurate simulation of flight dynamics of a spaceplane with programmable GNC parameters? I have a copy of "Fundamentals of Astrodynamics" by Bate, Mueller et al and I would love to do something with it this holiday season. I say simulation because all the rest of the stuff seems to cost a lot. I am real…

> I have a copy of "Fundamentals of Astrodynamics" by Bate, Mueller et al and I would love to do something with it this holiday season.

What do you plan on doing with it? I'd love to hear more about what the book is about and a project you might do.

Re: Challenging projects every programmer should try (2019)

#99
post #98
post #32

I would really love to try my hands on something much more physical, like a robot; or a drone with autopilot; maybe accurate simulation of flight dynamics of a spaceplane with programmable GNC parameters? I have a copy of "Fundamentals of Astrodynamics" by Bate, Mueller et al and I would love to do something with it this holiday season. I say simulation because all the rest of the stuff seems to cost a lot. I am real…

> I have a copy of "Fundamentals of Astrodynamics" by Bate, Mueller et al and I would love to do something with it this holiday season. What do you plan on doing with it? I'd love to hear more about what the book is about and a project you might do.

https://books.google.com.au/books?id=UEC9DwAAQBAJ

is the direct link to the Google Books overview with sample pages, table of contents, etc.

Re: Challenging projects every programmer should try (2019)

#100
post #95
post #24

While writing a text editor, a compiler, an operating system, or a raytracer might make you a better programmer, it won't make you a better software engineer. In fact, it might make you worse at software engineering, because it embodies the disastrous "Not Invented Here" doctrine. Hackers like to obsess about Big-O, data structures, HoTT, and other high-theory stuff, yet the following skills, essential for software e…

> In that spirit, I offer the following alternative challenge: Create a web search engine. Yea, no thanks. If I'm going to work on something in my spare time, I am going to work on something that I am interested in and find fun. I generally loathe the dirty work often involved in software engineering and debugging all of these dependencies all the time. It's exhausting. Doing things from scratch puts me in charge. An…

> And I mean, creating a search engine is the ultimate "not invented here" project. I'd just pay for and use Google, Bing, or whatever else API to do things for me. So it doesn't even make sense in the context of your objections.

Except that none of the established search engines actually does full-text search (anymore). There is no way to prevent those engines from breaking apart and rewriting your query as they see fit. No matter how many quotation marks you put around it, and even if you enable "Verbatim" mode or whatever.

So if you just implement the option to do that (which is actually the default if you leverage a standard FTS library), you already have something that AFAIK you can't get anywhere else. Then you can work on kicking the blogspam out of your index, and before long you will have a search engine of real value for yourself (and possibly others).

Or, you can build a crappy clone of a text editor from the 70s.

Post reply on HN