Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @dan@d.sb

  • 1 Post
  • 857 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle
  • That really depends on the company. At big tech companies, it’s common for the levels and salary bands to be the same for both generalists (or full stack or whatever you want to call them) and specialists.

    It also changes depending on market conditions. For example, frontend engineers used to be in higher demand than backend and full-stack.







  • Your data really isn’t worth that much.

    Also, it’s a common misconception that large tech companies like Google and Meta sell your data. They don’t. The data is what makes the company valuable - they’re not going to give away their competitive advantage. Instead, advertisers can target people based on the data. The advertisers never actually see the data nor exactly who their ads are reaching (it’s just aggregate anonymized data).

    On Google and Facebook, even individuals can use the same tools that large advertisers use to list their ads, and see exactly what they see.






  • I took down the home page of one of the top 5 websites for around 5 minutes.

    There were two existing functions that were written by a different team: An encode method that took a name of something (only used internally, never shown to the user) and returned a numeric identifier for it, and a decode method that did the opposite.

    Some existing code already used encode, but I had to use decode in my new code. Added the code, rolled it out to 80% of employees, and it seemed to work fine. Next day, I rolled it out to 5% public and it still seemed okay.

    Once I rolled it out to everyone, it all broke.

    Turns out that while the encode function used a static map built at build-time (and was thus just an O(1) lookup at runtime), decode connected to a database that was only ever designed for internal use. The DB only had ten replicas, which was nowhere near enough to handle hundreds of thousands of concurrent users.

    Luckily, it’s commonplace to use feature flags changes, which is how I could roll it out just to employees initially. The devops team were able to find stack traces of the error from the prod logs, find my code, find the commit that added it, find the name of the killswitch, and disable my code, before I even noticed that there was a problem. No code rollback needed.

    That was probably 7 years ago now. Thankfully I haven’t made any mistakes as large as that one again!

    Always use feature flags for major changes, especially if they’re risky!





  • Otherwise I feel like it’s a bit pointless to put so much work into a system that can’t be kept secure,

    You just need to recompile stuff when needed :D

    I think it’s designed mostly to be a learning experience rather than as a daily driver. It serves that role very well!


  • dan@upvote.autoLinux@lemmy.mlNiche Distro Users: Why?
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    1 month ago

    Kinda enjoying the process of piecing stuff

    At the risk of sounding crazy… You might enjoy Linux From Scratch (LFS) and Beyond Linux From Scratch (BLFS). Maybe not as a daily driver, but it’s a great way to learn how everything works, since (as the name suggests) you build everything from scratch. No package manager, just tarballs of source code. It really helps with getting an understanding of how everything works.

    BLFS even includes instructions for building Xorg and all the major desktop environments.



  • e.g. outlook replaces links in mails so they can scan the site first. Also some virusscanners offer nail protection, checking the site that’s linked to first, before allowing the mail to end up in the user’s mail client.

    Proofpoint does this too, but AFAIK they all just change the link rather than go to it. The link is checked when the user actually clicks on it. Makes sense to do it on-demand because the contents of the link can change between when the email is received and when the user actually clicks it.