• 0 Posts
  • 97 Comments
Joined 2 years ago
cake
Cake day: June 22nd, 2023

help-circle
  • Lol did it solve anything though?

    If you actually watch the full episode, the timeline of events is:

    • Someone rents a new house and finds a skeleton in the marsh behind it. It’s a ~30 year old woman who died in the winter and was bludgeoned and stabbed repeatedly.
    • They send away for DNA sequencing but the lab doesn’t get back to them for like a year and half.
    • In the meantime they look at missing persons cases (over 100 in North Carolina they state, though presumably ~half that once you filter for skeletal women)
    • They determine that this woman’s case seems most likely based on all the other details about her case. The forensic tech who’s oddly interested in how much pain people feel as they die is interested in using “impose an image of a skull on a face technique” to see if it matches.
    • She reaches out to a skateboarding computer science professor who uses gimp to paste a semi transparent layer of the skull on top of a picture of that victim’s face and thinks it probably maybe matches.
    • They get fed up with the DNA lab and send it to a second one that responds in three weeks confirming it was who they thought.
    • They talk to the victim’s friends who point out what party she was at the night she disappeared.
    • The people at the party say that she was hanging out with this one big truck driver after everyone else. His story has been that she walked home after everyone else left, in January, for 7 miles.
    • They interview him a few times and he eventually says that they had sex that night and she belittled him for not getting it up and he pushed her and she he hit her head on the nightstand and he left and she was fine when he left.
    • He’s convicted of murder and dumping her body because that’s an obvious crock of shit.

    Kinda feels like the whole GIMP escapade was just a waste of everyone’s time and all it took to solve the case was basic police work in terms of interviewing people who saw her last. By the time they tried GIMP they already had a prime missing person that they thought it was, and they wouldn’t have had to try gimp if they just went to a second / competent DNA lab immediately. The way they present it is a little unclear, but it sounds like they didn’t even pull the suspect in for further interviewing until they finally got the DNA confirmation for who it was.





  • You always have to learn the processes in a new company, this is just part of that.

    This thread seems entirely filled with people who seem to not grasp my core point.

    Yes you do, but in most cases, no you shouldn’t have to. Software should be intuitive. If it’s not, it’s more efficient to write software that is, rather than waste time constantly training everyone on inefficient software. This is literally one of the core tenants of the agile manifesto.




  • That’s fine and you don’t need to. But don’t knock it if you haven’t even taken time to learn it.

    The literal entire crux of my point is that core processes at a company should have intuitive software that doesn’t require weeks of training.

    So yes, I will knock VIM if you decide to use it as your company’s baseline coding environment. That’s dumb because it raises the floor for no reason and forces everyone through a bunch of training when they don’t need it to actually do their job if their software was intuitive.

    If you want to personally use it to do something powerful I have no issue with that, same way I have no issue with devs writing themselves bash or node scripts, what I have an issue with, is using it as the baseline. It literally requires training just for most devs to be able to exit it, and again, this is when tools like VSCodium have existed for years and are perfectly capable of handling large files.


  • Yes, ones who value time and efficiency.

    Why would you waste time teaching your devs a series of arcane commands to accomplish basic tasks that GUIs make obvious?

    I get it when you’re a sysadmin or embedded hardware dev who needs to access the file system in CLI only environments, but outside of that it’s just waste of training time and resources to build your standard dev environment around unintuitive tooling when stuff like vscodium exists.


  • Me:

    Be in a professional job, have to use crappy corporate software that takes weeks of training to use because it’s UX is absolute trash.

    Decide, ‘fuck this, I know I can do better’, spend months teaching myself coding, convince my company to pay me to write scripts so I can do it full time.

    A few years later, finally transition fully into the world of software development by taking an intermediate dev job at a well known major company… only to find my colleagues building our dev environments around VIM and not seeing an issue with it :/

    Good software does not require training or documentation, and that’s a hill I’m willing to die on.


  • masterspace@lemmy.catoProgrammer Humor@lemmy.mlIs that bad?
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month ago

    Fair point, I would argue that it’s not e entirely fair to compare a mobile OS that basically eschews backwards compatibility, for a desktop OS that can still run 30 year old applications, but it’s not entirely unfair either, they’re still both OSes and lots of the complaints have nothing to do with the burden of legacy support.



  • masterspace@lemmy.catoProgrammer Humor@lemmy.mlIs that bad?
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 month ago

    Oh I don’t think it remotely is. I just find it irritating that someone sees lots of complaints about the most popular thing and takes that as an indication that it’s bad, and ignores the indication that it’s not (it being the most popular thing).

    Lots of complaints about something popular literally means nothing on its own. The content of those complaints have validity, but there’s nothing to learn from their metadata.


  • masterspace@lemmy.catoProgrammer Humor@lemmy.mlIs that bad?
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month ago

    React Native’s new architecture is not that bad.

    You basically just got a single lightweight JavaScript thread that runs your rendering and updating logic, and then all the components are bound directly to underlying C++ native components.

    I would still expect the start menu to be aiming for zero dependencies and as fast a start as humanly possible, but it’s not that crazy compared to something like Electron (which itself is not as inherently bad as most people make it out to be).

    The real problem with slow web apps has less to do with the architecture of the apps, and more to do with them letting developers build apps really quickly and easily, meaning that you often have apps built by developers who don’t entirely know what they’re doing and introduce tons of inefficiencies like double rendering etc.



  • I started my programming career teaching myself to script and code to write tools to automate large aspect of my electrical engineering job. Eventually I hit the point, where my tools were getting huge and complicated and I realized that my professional software skills were lacking and I couldn’t just keep producing this untested spaghetti code and hope to actually get things done in manageable way.

    I then left for the world of professional software engineering, and in the time since, I’ve seen two companies that actually build software properly, and three companies producing worse code with worse practices than my self taught code from years ago.

    Quite frankly the world of software development is downright embarassing to work in at times. I don’t think we necessarily need to gatekeep software development with engineering degrees, but I do think that all developers should be required to take engineering ethics courses to understand their own responsibilities to push back and say no, this is not done and shippable until it’s properly built and documented.



  • Honestly, this is a pretty badly written and researched article for someone that likes writing so much.

    Like, just the opening two paragraphs about Microsoft controlling document formats … They repeat the same information in both paragraphs and give a rather incomplete history of document formatting.

    It’s also wild to write that many words about Markdown and never discuss its connection to HTML and its foundation in formatting via declarative intent rather than imperative formatting instructions (i.e. in markdown you dont style your title by saying bold / underling / font-size:20, you declare your true intent which is this is the top level title / heading, but that all comes from the underlying structure of HTML which markdown is basically just a simplification of.