• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle






    1. Those apps are simple
    2. Those apps target a wide audience, hence have more budget as a result
    3. Those apps are made by large, well oiled (you’d hope at least) companies. You don’t want my honest opinion on most small software development boxes. This industry grew faster than mentors became available for the newbies, so many devs including seniors still don’t know what they are doing.



  • Sorry for the late reply, the lack of a red envelope makes me not notice replies.

    People on election day have to decide if they go voting at all. This is a big deal, it’s what most of the campaign in the ridding is focusing on changing (you want to make sure all of your voters go vote, that is top priority in an election).

    Having a party that is a bad fit for you is demotivating and likely­ to reduce turnout. That is what I mean by “likely to vote”. It’s not the right wing option that people will go for. It’s the comfort of staying home and not bothering to vote for a “lib” if you’re a progressive, or for a “commie” if you’re a lib. For some people, the NDP is already too far right…

    So yeah, some of the support of the NDP would transfer over to the liberal party, but definitely not all. And that’s not to mention all of the crazy people who can go from NDP to tories at the drop of a hat (voters have shallower roots than the base, or have irrational hatred of specific politicians or parties) or who would just vote Bloq Québécois or something else.




  • Generally, you can replace some comments with variable names or comment names. Which means you must already be in the habbit of extracting methods, setting new variables to use appropriate names, and limit context to reduce the name (Smaller classes and methods means shorter names can be just as expressive, because the context is clearer). It lowers the number of wtfs per minute you get reading code before you even need whole sentences to explain why things are done in a certain way, because the names can be a powerful hint.

    But realistically, you end up needing comments for some things anyways.



  • Yes and no. I mean sure, if you are going to leverage this to gain a significant edge in the market, that works.

    If you add a tool to the project, that you need to understand to maintain some parts of it, which adds to the learning curve of someone joining said team, then the gains have best be worth the effort.

    We adopt so many librairies/plugins/tools over time that adding more complexity than you need this way is just terrible.


  • Yeah, but it’s easy to overuse it. If your for loop is much longer. For a few lines I’d agree, don’t bother using something longer.

    Code should scream out it’s intent for the reader to see. It’s why you are doing something that needs to be communicated, not what you are doing. “i”, “counter” or “index” all scream out what you are doing, not why. This is more important than the name being short (but for equal explanations of intent, go with the shorter name). The for loop does that already.

    If you can’t do that, be more precise. At the least make it “cardIndex”, or “searchIndex”. It makes it easier to connect the dots.




  • It has a rocky start, and a lot of cruft from that era sticked around.

    There are also a lot of horrible legacy projects from the pre-ES5 era which are a pain to work with. Often older projects were coded either before people knew how to do javascript right, or before the devs who wrote it knew how to write javascript right.