Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Overthinking it and the value of simple solutions (2019)

korecki.me

Post reply on HN
Print view View original

51–58 of 58 posts

Re: Overthinking it and the value of simple solutions (2019)

#51

Post by jariel »

cryptica wrote: post #9

Sometimes it requires a lot of thinking to come up with simple solutions. Usually you need to consider a lot of alternative solutions in order to come up with the simplest solution and that takes time and a lot of thinking and a deep understanding of the requirements. When I start a new complex project, in the early stages, there are entire days where I'm just thinking about stuff without writing any code. Then as th…

Came here to validate that.

"Overthink it' first, and then smooth it down to its essential simplicity" is usually the process.

FYI the reason I don't like the musical analogy is because in that scenario, the tooling can easily overwhelm the creative process. You get caught up in the tools and literally never think about the problem.

I suppose a software analogy be might be using 1000x various frameworks to try to do something: you'd never get past the frameworks.

Re: Overthinking it and the value of simple solutions (2019)

#52

Post by jariel »

qwerty123457 wrote: post #44
uk_programmer wrote: post #38

Earlier quoted context omitted.

> still unsure i follow. i must be missing something... react does not prevent anyone from using jquery afaik. in fact, anyone can go ahead and use jquery with react if they want. React / Angular JS etc tend to require spending a lot of time learning how it works first. Then you have to build almost all your application around it. This can take a lot of time, which pushed up costs and complexity. If you are building…

React is easy as hell to learn nowadays, I'd say about as easy to get into as as PHP. Any semi-experienced developer will be writing production grade code after at most a week of learning.

So this isn't quite true for a few reasons.

Reach is quite a different abstraction than we are used to, it's huge and prolific.

It generally takes some time to get used to it. Though one might be able to do 'some production quality stuff' in a week, generally speaking, there's far too much that anyone is going to master in a week.

Re: Overthinking it and the value of simple solutions (2019)

#53

Post by Plugawy »

cryptica wrote: post #9

Sometimes it requires a lot of thinking to come up with simple solutions. Usually you need to consider a lot of alternative solutions in order to come up with the simplest solution and that takes time and a lot of thinking and a deep understanding of the requirements. When I start a new complex project, in the early stages, there are entire days where I'm just thinking about stuff without writing any code. Then as th…

> Sometimes it requires a lot of thinking to come up with simple solutions.

Author here - I should have tweeted that instead of writing a blog post

Re: Overthinking it and the value of simple solutions (2019)

#54

Post by uk_programmer »

onemoresoop wrote: post #49
uk_programmer wrote: post #46

Earlier quoted context omitted.

I've worked professionally with Angular 2 and 4 and it just a PITA. People either just end up using it like the JavaScript version of ASP.NET WebForms or you end up with one guy that really knows it inside out and nobody understand the code he has written. It hides too much of what is going on for my liking and if you break something a lot of the time it is impossible to diagnose without slowly pulling the code apart…

Things have gotten better with Angular 7 but, my experience is different from yours. I built my own project in Angular 7 , followed all the guidelines and maintenance has been a non issue and the project is very clean. But I could see things going crazy complicated if more devs add code to the project, I hear your frustration

It maybe better. Realistically I am going to have to learn either Angular or React if I want contracts in the future.

Angular 4 was a lot better than Angular 2 as there were more docs available. One of my major frustrations at the time was that you couldn't just pull up an example of how to do something that I would imagine would be pretty common and you were scrounging around for blogs or things were behind a paywall.

Re: Overthinking it and the value of simple solutions (2019)

#56

Post by collyw »

Ididntdothis wrote: post #22
arethuza wrote: post #6

Earlier quoted context omitted.

While not disagreeing with your point, it is also worth noting that in some contexts developers are regarded as unemployable if they don't have experience with whatever the latest technology is so it is hardly surprising that people use every opportunity they can to get exposure to the latest tools. 'Modern' hiring practises cause a lot of problems.

That’s a real problem. I feel that me and my team have done serious damage to our resumes by solving the last few projects in a simple and straightforward way. Instead we should have done cloud, containers, React and whatever even if it made the solution very complex. This became really clear a few months ago when management two layers up gave one of our projects to another company who will move it to AWS. There were…

Do you think this is the reason for some of the supposed ageism in the industry?

I have been doing this for 17 years and I prefer server side rendering and jQuery to React / Angular plus some REST API I know it will take around half the code, and will be easier to debug and maintain. It doesn't make my CV look good though.

Re: Overthinking it and the value of simple solutions (2019)

#57

Post by onemoresoop »

uk_programmer wrote: post #54
onemoresoop wrote: post #49

Earlier quoted context omitted.

Things have gotten better with Angular 7 but, my experience is different from yours. I built my own project in Angular 7 , followed all the guidelines and maintenance has been a non issue and the project is very clean. But I could see things going crazy complicated if more devs add code to the project, I hear your frustration

It maybe better. Realistically I am going to have to learn either Angular or React if I want contracts in the future. Angular 4 was a lot better than Angular 2 as there were more docs available. One of my major frustrations at the time was that you couldn't just pull up an example of how to do something that I would imagine would be pretty common and you were scrounging around for blogs or things were behind a paywal…

Look up kudvenkat on youtube. He has very clear and succinct (and no bs) tutorials broken down on easily digestible features. On each short tutorial he provides a recap at the end. Watch some angular playlists of his and see if they could be of any help to you. They helped me.

Re: Overthinking it and the value of simple solutions (2019)

#58

Post by uk_programmer »

onemoresoop wrote: post #57
uk_programmer wrote: post #54

Earlier quoted context omitted.

It maybe better. Realistically I am going to have to learn either Angular or React if I want contracts in the future. Angular 4 was a lot better than Angular 2 as there were more docs available. One of my major frustrations at the time was that you couldn't just pull up an example of how to do something that I would imagine would be pretty common and you were scrounging around for blogs or things were behind a paywal…

Look up kudvenkat on youtube. He has very clear and succinct (and no bs) tutorials broken down on easily digestible features. On each short tutorial he provides a recap at the end. Watch some angular playlists of his and see if they could be of any help to you. They helped me.

I might very well do that.Thanks
Post reply on HN