django @ django @sh.itjust.works

Posts

1

Comments

3

Joined

2 yr. ago

There's a difference between iterating on your code patterns until you get something working and iterating on the solution as requirements evolve. You're only two months in so you still have loads to learn, but eventually you'll come to know all the "best practices" so that when you're presented with a problem, you can immediately know what the ideal solution should look like. The caveat there is that the ideal solution is subject to change as the situation changes.

This is why it's important to have API access available (for a reasonable price, let alone free). The people who want Twitter data are now loading tons of completely unnecessary and heavy multimedia content just to parse it manually for the comparatively light text data they care about. It would literally save Twitter money to give the data away.

As an experienced programmer, I can say there's nothing inherently wrong with hardcoding data. If you're not presented with clear requirements up front (i.e. all the different use cases your code should handle) then it makes more sense to get something working and refactor as you go. In your case you said the data was subject to change, which doesn't necessarily mean you could abstract it out from the start (unless you were told exactly how it would change). In general, however, software development is all about iteratively refining your assumptions about how things should work while simultaneously juggling the changing demands of stakeholders. One of the most useful rules of thumb is the DRY approach (don't repeat yourself). This is complemented by WET (write exactly twice). Together this means that if you find yourself repeating logic three times, that's enough for you to refactor into a single, generalized function. Repeating twice is generally fine because your third use case might be sufficiently different that a premature refactor is a waste of effort. As you gain more experience programming, you'll find it's less about technical proficiency and more about working efficiently, creating fewer headaches, etc.