3 ms·
Programming isn't computer science, so that can be misleading coming from that into programming/software engineering. Also, programmers may write a blog articl
by ilaksh 11y ago
Programming isn't computer science, so that can be misleading coming from that into programming/software engineering.
Also, programmers may write a blog article that represents a perfectly crafted solution and present it as the norm even though they really have to settle for hacks in their day job.
And people will often present themselves as being experts in a subject when in reality they just found out the technology existed two days ago. No one can be an expert on every new system or even most of them. The most relevant technology is often something new to learn.
Also, different jobs vary wildly in terms of schedule, how much time there is to experiment with solutions, how much actual factoring/testing/engineering is expected, etc. Most project phases or jobs in general fall short of the ideal in this regard.
Also, people may have just plain misrepresented to you what effective engineering actually is.
I think to be effective at solving tech problems you _have_ to guess and then see what happens and then adjust. That's what engineering is. Its based on the scientific method.
Physics is complex, especially information technology. And you can't develop everything from scratch. You have to take advantage of other people's work, guess how it will fit together best. But it is always a guess because the laws of physics make it impossible or impractical to figure out what the system is going to do without running it first. So you try out different ideas or designs and adjust. In a feedback loop.
As far as getting lines of code out the door, you want the fewest lines of code that are practical given time constraints on factoring. The ideal might be no lines of code sometimes when you can use an existing solution.
Anyway, yes, they are guessing, because of the laws of physics.