• 3 posts
  • 26 comments
Joined 3 years ago
Cake day: August 6th, 2023

Hi,

I have a friend who is looking to run a few simulations he has implemented in python and needs around 256GB of ram. He is estimating it will take a couple of hours, but he is studying economics so take that with a grain of salt 🤣

For this instance, I recommended GCP, but I felt a bit dirty doing that. So, I was wondering if any of you have a buttload of memory he can burrow? Generally, would you lend your RAM for a short amount of time to a stranger over the internet? (assuming internet acccess is limited to a signle ssh port, other necessary safeguards are in place)

  • Petkauskas’s article describes the discovered breach as “a plethora of supermassive datasets, housing billions upon billions of login credentials” that have been sourced from “social media and corporate platforms to VPNs and developer portals.” This data is sourced from “30 exposed datasets” that researchers say contains “tens of millions to over 3.5 billion records each.”

    To be clear, this is not a new data breach, or a breach at all, and the websites involved were not recently compromised to steal these credentials

    Regardless of whether this involves freshly leaked credentials or not, it might be a good time to freshen up your logins. Hackers’ jobs are getting easier by the day.

  • Hey, I was fired last July and I went through the same process, I actually asked a similar question on Lemmy and the feedback I received helped a tonne in landing more interviews.

    Here are the steps I believe helped me:

    1. Make sure your CV is machine parseable, search for open resume, upload your cv see what it detects. Ideally, generate your CV using that tool.
    2. Create your own portfolio website, here is mine for reference https://souperk.gr/ (I have a public repository, feel free to copy if CSS isn’t your strong suite)
    3. Check that toggle on LinkedIn to signify you are actively searching atm (don’t remember how, but you should see a ribbon on your avater if it’s active)

    For me, landing more interviews was the hard part. Once I got a few interviews going, landing an offer was easy.

I just finished reading this book and decided to share my experience with it.

About the Book

Continuous Architecture in Practice is a sequel to Continuous Architecture both written by Murat Erder, Pierre Pureur, and Eion Woods. The authors attempt to address feedback from their 1st book by navigating the reader through the Trade Financs eXchange (TFX) case study.

The book starts with a brief introduction to the core concepts of Continuous Architecture, including its 6 principles, as well as its essential activities:

  1. Focus on quality attributes
  2. Drive architectural decisions
  3. Know your technical debt
  4. Implement feedback loops

From then on the book switches focus to common architectural concerns:

  1. Data
  2. Security
  3. Scalability
  4. Performance
  5. Resilience
  6. Emerging Technologies

Each concern is tackled in a separate chapter that features an introductory quote, a definition along with some historical context, a list of issues an someone should keep in mind when architecting for that concern, a list of tactics, and a further reading section.

My Opinion

Overall, I liked reading the book, it gave me a lot of inspiration and a desire to learn more about particular topics. The book assumes a certain level of familiarity with software engineering which helps it focus on general concerns and avoid implemention specific details.

I particularly liked the Emerging Technlogies chapter as it offers a healthy view on AI, ML, and shared ledgers. It helps remove the fairy dust that’s blinding our industry, and instead focuses on meaningful changes that actually provide value to a product.

Also, as someone with experience in software security I appreciated the focus on shifting left security concerns.

Who Should Read This

In my opinion, every software engineer can benefit from reading this at some point in their career. However, I wouldn’t recommend it to a junior, if you are not already familiar with the topics covered in the book it could be intemediating.

PS I am not affiliated with the book or its authors in any way. I am just a person that read a book they liked wanted to share my experience.

  • I would give myself a solid 4.2/5 on python.

    • I have in deepth knowledge of more than a few popular libraries including flask, django, marshmallow, typer, sqlalchemy, pandas, numpy, and many more.
    • I have authored a few libraries.
    • I have been keeping up with PEPs, and sometimes offered my feedback.
    • I have knowledge of the internals of development tooling, including mypy, pylint, black, and a pycharm plugin I have created.

    I wouldn’t give myself a 5/5 since I would consider that an attainable level of expertise, with maybe a few expections around the globe. IMO the fun part of being really good at something is that you understand there still is to learn ❤️

  • I’ve had a very tough time finding my first position as a junior dev

    The hiring landscape for software engineers/developers is a mess for the past year or so. You shouldn’t internalize the experience, most likely you are just unlucky.

    A few things to consider for finding a job:

    1. Utilize your connections, a lot of hiring still happens through connections. If you have attended a university/college/bootcamp reach out to your professors and check if they can refer you to any positions.
    2. Make sure your CV can be parsed by tools. Try uploading your CV on open resume, if it’s not parsed correctly you might want to update it.
    3. Create a portfolii website, it’s a great way to illustrate your skills. Also, others here can check it out and offer advice.
    4. Update your LinkedIn profile, make sure to check that open for recruiters thingy.

    If you want to learn more about react I am happy to have a chat with you (no fee), feel free to DM me.

Hi,

I am looking for a remote senior software engineer position. Most of my career I have been using connections to move from one job to another but this time I haven’t had the luck, so I am mostly blindly applying through LinkedIn.

I know the general tips but I would like to get some more specific tips to improve my chances.

How can I make my CV stand out? I feel I am getting rejected by positions that are way below my qualifications. I have wondered if I should be updating my CV according to the stack of the position I am applying for. Throughout my career I have focused on building transfarable skills and as a result I have worked with a wide variety of technologies and it feels like I am being penalized for that.

Are there any job boards that may be better than LinkedIn? I am tired of skimming through ads about fintech and AI positions. I am not interested in those and I would prefer to work somewhere that I genuinely I am contributing something in the world. Also, I would be interested on job boards on the Fediverse, especially if it meant that my resume is read by humans and not machines.

How can I avoid time wasters? I had applied to Canonical, after 8 interviews and a bunch of offline steps, I was rejected. While the interviews were fun, I feel I have wasted a lot of time and energy for a someone that was not genuinely interested in hiring.

Anything else I should be paying attention to?

  • I am definitely guilt for that, but I find this approach really productive. We use small bug fixes as an opportunity to improve the code quality. Bigger PRs often introduce new features and take a lot of time, you know the other person is tired and needs to move on, so we focus on the bigger picture, requesting changes only if there is a bug or an important structural issue.

  • Me neither buddy, me neither…

    Falsehoods About Time: … Time always moves forwards.

    I had to learn this the hard way… I was working at a platform that pulled measurements from sensors. The sensors did not declare the timezone for the timestamps of the measurement and the platform broke down twice after daylight saving. The first time there were duplicated records which caused conflicts and the second one we weren’t handling impossible timestamps.