• 0 Posts
  • 60 Comments
Joined 2 years ago
cake
Cake day: June 9th, 2023

help-circle
  • A good (technical) interview should feel like a fun conversation with a friend on the topic at hand.

    Most people are trying to see if they’ll like you, and that you can pull your weight. Assuming you’re qualified the second part isn’t an issue.

    Practice with a friend or family member. Get comfortable talking about yourself, and post experiences. Get comfortable asking follow up questions. That comfort will let you be yourself during the interview so the interviewers can actually gauge your fit.


  • Here’s my testing recommendations

    Testing methodology

    To get consistant results, use a consistent method of test. If you’re downloading a large file, always test by downloading that same file from that same source. If you’re using a speed test service, use the same speed test service with the same server. If you’re using a tool like iperf3, always use the same tool against the same iperf server.

    Potential issues

    Networks can fail from hardware issues, software issues and infrastructure issues. Since you don’t control 99.9% of the infrastructure if the internet is involved, lets leave that for the last option.

    Hardware Issues

    The hardware involved you control are mostly your NIC, and your Remote Connection. For wired ethernet at home, this is likely a physical ethernet port on your computer on one end, and another physical ethernet port on a switch/router/ap provided by your ISP.

    Testing Wired Hardware Issues

    • Using the same switch and cable, run a speed test on another computer. If the issue persists, the problem is not with your computer, if it resolves, its related to your computer.
    • Using the same computer and cable, run a speed test on another switch. If the issue persists, its not the switch or cable, its your computer, if it resolves, its not your computer.
    • Using the same computer and switch, use a different cable. If the issue persists, it’s not the cable and its either your computer or switch, if it resolves, its the cable.

    With these three you can figure out what device is causing the problem.

    Testing Wireless Hardware Issues

    The hardware involved is the wireless NIC in your computer, the environment your wifi signal is in, and the wifi AP. The steps are much the same as testing for a wired issue

    • Using the same AP and physical location, run a speed test on another computer. If the issue persists, the problem is with the AP or location, if it doesn’t it may be your computer
    • Using the same computer and physical location, run a speed test on another AP. if the issue persists, the problem is with your computer or location, if it resolves, it may be the AP
    • Using the same computer and AP, run a speed test in another physical location. If the issue persists, the problem is with the computer or AP, if it resolves it may be the environment

    Software Issues

    The issue could be software related. Something like the drivers running on your laptop or connection point.

    Testing Computer Drivers

    You’ve already done this for your computer by dual booting. This proves the issue is not driver related, since the problem persists with two different sets of drivers.

    Testing Connection Point Drivers

    • You have less control over the drivers on your switch/router/ap. If the hardware tests resolve when using a different AP, then you can attempt a firmware upgrade/downgrade before replacing the physical device. This isn’t usually worth the hassle since ISPs are quick to replace them with a service call.

    Testing Computer Configuration

    Your network settings could be misconfigured.

    • If you are using DHCP, turn it off, and enforce a speed negotiation, IP address, subnet mask, and DNS server and try again. If the issue persists, then it’s likely not related to your configuration. If it resolves it probably is.
    • If you are using a static configuration, turn it off and use DHCP. If the issue persists, it’s likely not related to your configuration, if it resolves, it probably is

    Infrastructure Issues

    If your home network is more sophisticated then an ISP provded router/switch/ap combo connected to everything over wifi and ethernet, theres more devices to troubleshoot. But if you have something like this, you probably already know what you’re doing a little bit and wouldn’t be making this post. But who knows! Re-run the process isolating each device and replacing it with something known good to identify whats causing the problem.

    As for the internet, it’s not a stable and safe place. Speeds vary drastically day to day. Internet weather happens and partial outages occur regularly. Don’t forget that the service your using to speed test could be the issue itself. It’s another component to isolate and test.

    Process

    Use the above steps to identify what device is causing the problem, and if its a hardware or software issue. Hardware issues are mostly resolved by replacing devices, while software issues are resolved with software updates and configuration changes.

    Good luck and god speed!







  • Pass uses GPG and git under the hood.

    You create keys to encrypt your data, and keep the encrypted data in git locally which can be cloned to github, gitlab and the like.

    It’s just files on your computer, so you can back them up that way, or use a thumb drive as a remote git repo and push to it.

    Day to day Type pass and tab complete to find the entry. Enter the command and be prompted to unlock it. It will then print the credentials to the terminal.

    To create a new password, you type and add command followed by a name and a text editor opens up for you to type credentials in, or it can generate them for you.

    To keep your backup up to date you just git push to the remote of your choice. I use github



  • lungdart@lemmy.catoLinux@lemmy.mlBSD Vs. Linux
    link
    fedilink
    arrow-up
    42
    ·
    9 months ago

    The majority of the Internet’s routing and switching architecture is BSD based. Historically it had the most stable and performant network stack of all the OSs.

    I used it extensively at one job in a previous life when I was a network appliance developer. It was rock solid and lightning fast. Tried it as a desktop at home and had a terrible experience.

    The little differences in the Unix commands used to drive me nuts as well…






  • lungdart@lemmy.catoAsklemmy@lemmy.mlWhat is Web 3.0?
    link
    fedilink
    arrow-up
    31
    arrow-down
    2
    ·
    1 year ago

    It’s a buzz word.

    Web 1.0 is just websites. They envisioned everyone had their own web site to blog on. Geocities, ISP hosting, web rings, link aggregators, and simple human curated search engines. That kind of thing.

    Web 2.0 basically meant APIs. You could stitch a weather API with a map API and make a weather map app. This kind of came true, but it wasn’t as free and open as people hoped for.

    Web 3.0 is supposed the intersection of the web and distributed apps. Think games on the block chain like crypto kitties. It’s mostly been a flop since blockchain based decentralization is slow, expensive, and difficult for users. That being said there are successful use cases like online wallet management and distributed exchanges (defi).