Just some Internet guy

He/him/them 🏳️‍🌈

  • 2 Posts
  • 158 Comments
Joined 2 years ago
cake
Cake day: June 25th, 2023

help-circle

  • It really depends, most people end up specializing into specific things they work on as software has generally become too big for single developers. We have people that only do frontend stuff so things look nice on the website, some only deal with the database and making sure we return results as efficiently as possible.

    I started off doing the typical full stack but I’ve since branched off into DevOps so now I’m responsible for a few hundred servers across the globe that I keep updated and running smoothly.

    Sometimes I work on new tools, sometimes I spend days tracking down weird problems, sometimes I’m rushing hotfixes because something is repeatedly crashing in production.

    It’s worth noting that because you can click through UIs these days doesn’t mean that scales as you go. You can go spin up your app in a container in the cloud mostly through UI, but soon enough the defaults aren’t enough. I manage several hundreds of instances across a few clouds, I’ll well, well past clicking next next next finish. It’s just an easy and visual way to ease you into things, especially for beginners, as all the options available to you are there to see along with little help tooltips explaining what a setting does.

    It also depends on what you do: if you work at a startup, clicking through Cloudflare’s dashboard is more than enough. When you have thousands of customers, you’re not managing the tens of thousands of settings you have to configure, you automate.

    Code can describe things (HTML, CSS, HCL), code can configure things (YAML, JSON, Ansible), code can program things (PHP, JavaScript, Python, Ruby, etc), code can query things (SQL), programming as a whole is very wide.



  • Arguably, if it was normal to sideload apps it wouldn’t be as much of a barrier to users, but they’ve been conditionned to think they need an app and the only place you can ever get them is the store.

    It’s a technical hurdle only because Apple decided they want to control everything, and same on Android because of Google’s ever increasing war on sideloading. You used to download an APK from the browser and it would go like “This is an app! Install?”, but now you have to go enable third party installation and all that, and now the whole Play Protect forcing developer validation coming up.









  • No, I would simply give them a box of condoms or whatever.

    If they’re gonna do it, they’re gonna do it, and as a parent, you’re way better off with your kids comfortable not hiding it because if there’s complications you can intervene quickly. If the condom broke, you want the kid to come to you so you can get plan B and not have to deal with an abortion a couple weeks or even months later. It’s also way better they get caught doing it at home vs in a car and now be on the sex offender registry.

    What you’re describing is abstinance and is common in religious families, and well know for being ineffective. Plus as you’ve described, it completely falls apart when bisexuality is involved, and it makes even less sense if it’s physically impossible to even get pregnant.

    The same extends to alcohol, drugs, porn, whatever evil vice people are worried. If your kid’s gonna do drugs, you want them to feel comfortable calling you if they have a bad trip, and also feel comfortable giving you the drugs so you can get them to the hospital and they can quickly identify what you’re on and give the necessary medications.

    They’re gonna learn about all that eventually, better they learn it from you. Punishment and “you’ll understand when you’re grown up” doesn’t work. If they’re old enough to ask, they’re old enough for the answers too.


  • Max-P@lemmy.max-p.metoFediverse@lemmy.worldTime for a purge
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    1
    ·
    2 months ago

    Free speech includes respecting speech you disagree with and speech that makes you uncomfortable.

    If the roles were reversed and you were lined up to be banned because you’re not siding with the “correct” side, you’d be crying abusive censorship.

    That’s what the downvote and block buttons are for.


  • Yes, a lot safer. Even bugs in the renderer or media player would typically be triggered by JavaScript by say, moving elements around really fast or whatever.

    Without JavaScript, the browser renders that page and that’s it, there’s no JS to modify it or open popups, nothing to dynamically load/refresh content. The most you can do without JS is animations and responding to simple events like changing the color of a button when the mouse is over it. So your only shot to attack this is the renderer during initial page load, once.




  • For all its flaws and mess, NFS is still pretty good and used in production.

    I still use NFS to file share to my VMs because it still significantly outperforms virtiofs, and obviously network is a local bridge so latency is non-existent.

    The thing with rsync is that it’s designed to quickly compute the least amount of data transfer to sync over a remote (possibly high latency) link. So when it comes to backups, it’s literally designed to do that easily.

    The only cool new alternative I can think of is, use btrfs or ZFS and btrfs/zfs send | ssh backup btrfs/zfs recv which is the most efficient and reliable way to backup, because the filesystem is aware of exactly what changed and can send exactly that set of changes. And obviously all special attributes are carried over, hardlinks, ACLs, SELinux contexts, etc.

    The problem with backups over any kind of network share is that if you’re gonna use rsync anyway, the latency will be horrible and take forever.

    Of course you can also mix multiple things: rsync laptop to server periodically, then mount the server’s backup directory locally so you can easily browse and access older stuff.


  • Also worth noting that the computations don’t have to be expensive either, it’s only there in cryptocurrencies to artificially limit the number of blocks generated on a public system and tie it into the reward system.

    So for a bank, that could be a plain single iteration of a sha256 hash, and once share everyone agrees those were the transactions and you can’t go back and change one without having to change the whole chain.

    Make it sha1 and you basically have git.

    A blockchain is more or less just an append-only database. Or even an append-only replication log with built-in checksums.



  • It helps hackers sure, but it also help the community in general also vet the overall quality of the software and tell the others to not use it. When it’s closed source you have no choice but to trust the company behind it.

    There’s several FOSS apps I’ve encountered, looked at the code and passed on it because it’s horrible. Someone will inevitably write a blog post about how bad the code is warning people to not use the project.

    That said, the code being public for everyone to see also inherently puts a bit of pressure to write good code because the community will roast you if it’s bad. And FOSS projects are usually either backed by a company or individuals with a passion: the former there’s the incentive of having a good image because no company wants to expose themselves cutting corners publicly, and the passion project is well, passion driven so usually also written reasonably well too.

    But the key point really is, as a user you have the option to look at it and make your own judgement, and take measures to protect yourself if you must run it.

    Most closed source projects are vulnerable because of pressure to deliver fast, and nobody will know until it gets exploited. This leads to really bad code that piles up over time. Try to sneak some bullshit into the Linux kernel and there will be dozens of news article and YouTube videos about Linus’ latest rant about the guilty. That doesn’t happen in private projects, you get a lgtm because the sprint is ending and sales already sold the feature to a customer next week.