[–] 2 points 1 year ago (1 child)

I don't get the concept of "learning" a specific programming language, you can't just sit down and learn the entire thing at once. You use it, google its weird quirks whenever you come across them and get better with it over time.
I've always been really language agnostic, which led to me being shifted into a Delphi team and then into a Typescript/React team. Didn't know anything about those languages when I entered the team but someone who's willing to just try their best can be a lot more desirable to a company than someone who thinks they can't do something just because they didn't spend time learning it "properly" first.

Also, might just be a regional thing, but the last time I went to one of those "I just finished university and want to network with companies" events, like 70% of the CS graduates were looking for Data Science positions. Seems like it's quite the saturated market.

  • source
  • [–] 23 points 1 year ago

    Oh bummer. You just spent 4 years building an extremely solid base in multiple different aspects of programming. How could you possibly ever be expected to find unique specializations?

    Tldr: University is a foundation you're expected to build on it.

  • source
  • Either learn the hottest new thing or the legacy thing everyone is stuck with, both will always be in demand. But the whole point of the field is to always be learning so starting a good habit of that now is key. Read and research and tinker. Contribute to open source. Follow people and projects on GitHub. The best software engineers are looking for problems to solve and then learning the tools required to solve them, not looking for problems that fit the tools they already know.

  • source
  • [–] 16 points 1 year ago

    Studying at a university is not a fancy job training.

    Do whatever pays your bills, and learn what interests you. Sometimes the latter will help with the former, but it would be silly to depend on that.

  • source
  • [–] 3 points 1 year ago*

    Also remember:

    As a rule, strong feelings about issues do not emerge from deep understanding.

    and:

    If you can't argue your position without attacking a person's character, you already lost the argument.

    By being humble and understanding that not everybody will perceive the world like you do, you will be able to engage in deeper conversations that foster more fulfilling relationships that can boost your well-being.

  • source
  • [–] [S] 1 point 1 year ago

    thanks for your thoughts. npm is popular for a reason and vanillajs doesnt scale very well. so any deps used could be an issue.

    i was also considering if with the webcomponent approach it could be “furture-proof” as it seems to be the rhetoric i hear around. im sure i wont have a great implementation any time soon, but id like to try out a few ideas to see if it holds-up. hopefully to lead to a “secure javascript ui framework” (which itself could be a whole discussion).

    but based on all the feedback ive recieved, it seem for the messaging app refactor, i’ll be fine to use react on it. which is great because i already have a working-ish demo.

  • source
  • parent
  • context
  • [–] 2 points 1 year ago (1 child)

    When working with web components, you will likely also end up with dependencies that you’ll install using npm (eg lit itself). Theoretically, the same supply chain attack can still happen this way and thus introduce malicious code in the web components JavaScript, see for example this article (first search result)

    You could write your own ui-library using whatever technique you deem to be safe, or you can stand on the shoulders of giants and start with a readily available one and adjust as needed. Security-wise I thinking would be better to ensure the frontend and backend are separate projects/applications that could (theoretically) be deployed on different machines and still exchange the necessary information through an api, so you’ll know that even if something happens on one end, the other wouldn’t necessarily be affected as well.

  • source
  • [–] 1 point 1 year ago

    For images with large blocks of solid colors and no gradients, frequently the opposite is true. Screenshots and avatars with solid(transparent) backgrounds are often smaller as png.

    It drives me nuts seeing things like tweets (white and black text) being shared with crazy jpeg artifacting. They'd be so much smaller and so much less ugly as png

  • source
  • parent
  • context
  • [–] 4 points 1 year ago (2 children)

    Everyone, go update your 2003 forum avatars.

    My friend, most people weren’t using PNG in 2003, especially for forum avatars. They were glitchy on browsers (IE) for almost a decade after that.

  • source
  • view more: ‹ prev