frankfurt_schoolgirl [she/her]

  • 2 Posts
  • 79 Comments
Joined 2 years ago
cake
Cake day: July 25th, 2022

help-circle









  • Honestly if you are applying for an internship you just need a finished product of some kind, ideally with unit tests. Make sure it has a pretty front end, works on mobile, and is deployed to a server. It should use at least some JS on the front end, maybe a framework like React if you’re interested in web dev. On the backend, make a server with Java and Postgresql. Make sure it has a CI/CD pipeline, which you can do for free with GitHub Actions. Make sure it has a server, which you can do or very cheap with AWS EC2 free tier and Let’s Encrypt. Put an MIT license in the repo. If I couldn’t think of anything, I would try making a Lemmy client, because this one does too much on the front end and is super slow as a result.

    There is a different way to go here, which is focus on your C skills and try to do low level or embedded development. I don’t know as much about this, but maybe some project involving an OS kernel or a piece of embedded hardware? Maybe something Arduino or RPI? The same idea applies that it should be in a GitHub repo with tests and documentation.

    Also, my hot take is that you don’t need to be that good at DS&A for entry level if you stay away from big tech companies. Like sure, Google will quiz you on big-O. But what if you were a developer for a grocery chain, or a bank, or a small web firm, as your first job? That’s what I did, and it has been chill and easy so far. And I haven’t gotten laid off like my FAANG friends.







  • frankfurt_schoolgirl [she/her]@hexbear.nettoLinux@lemmy.mlThoughts on this?
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    1
    ·
    6 months ago

    I’ve been using Wayland for 5 years. There were a few bugs in the beggining, but now it works great. These threads are such a waste of time.

    I have over 100 confirms X11 developments

    That’s great dude. Why don’t you go maintain it then, apparently nobody else wants to: https://www.phoronix.com/news/RHEL10-Removing-X.Org

    Wayland took too long

    Look up how long btrfs has been in development, or at audio subsystem churn. These things take time, because it’s mostly volunteers working on them.

    Systemic complexity has doubled in the last two years

    What does this even mean?

    Mir was better

    It turns out the Canonical dumping random stuff over the wall is not the same as creating a legitimate open source community around a project.

    Unfixable amount of race conditions

    As if there’s never been a synchronization bug in X… But also System76 and others are writing Wayland compositors on Rust anyway.