• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle

  • Before I replace it with something that won’t catastrophically collapse when the wind blows the wrong way, I get some sort of sick satisfaction out of doing autopsies on the house-built-of-matchsticks “solutions” that users come up with and I don’t know why. Some of them are truly fascinating and make you wonder how someone could possibly arrive at that conclusion based on what they were actually try to achieve.

    It’s also why if I’m asked to implement something, my first question isn’t “When does this need to be done?,” it’s “What exactly is the problem you’re trying to solve?”

    What a user asks for and what they actually need very rarely intersect.


  • tool@lemmy.worldtoGreentext@sh.itjust.worksAnon flies air Chad
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    7 months ago

    I literally cannot tell the difference.

    Source: am manager, and sometimes my underlings don’t toil hard enough in the PowerPoint mines.

    You should mercilessly berate them until morale improves, that’s MBA 101.

    You’re gonna be back in the PowerPoint mines if you don’t fix your soft-hearted attitude.








  • They really don’t, though. Inclusion/exclusion operators work most of the time, but it’ll still return results with explicitly-excluded keywords. It also fucks up results by returning entries with similar words to your query, even when you double-quote a part of the search term. Advanced queries that use booleans and logical AND/OR don’t work at all anymore, that functionality has been completely removed. It returns what it thinks you want, not what you actually want, even when explicitly crafting a query to be as specific as possible.

    I use Kagi for search now and it’s 1000x better, especially when researching technical issues; it’s like when Google actually respected your search terms and query as a whole.







  • tool@lemmy.worldtoProgrammer Humor@lemmy.mlIt's not great
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    On GitLab, you start from a docker image, so it’s harder to setup some things but easier for others. If you are very good at docker and don’t mind making your own images just for CI purposes, then go ahead.

    I think I’d probably consider myself at/near expert-level with Docker, but CI/CD runners instanced in containers just doesn’t work for some of our workloads.

    As an example, some of our projects have a bunch of Docker images that get built via their own Dockerfiles in the repo, are ran and discarded during the workflow, and each one is modifying the checked-out source tree in some fashion (NPM stuff, composer, whatever, etc), and then a final prod Docker image is built and tested from that source repo tree that has been modified by the Docker containers built/ran/discarded during the workflow. So in Gitlab, it sounds like we’d be running Docker in Docker for some projects.

    You ever ran Docker in Docker? It’s temperamental at the very best and there are a thousand gotchas associated with it, not to mention having to worry about how many variable scopes deep you are and keeping track of that, how to properly bind mount volumes into the nested Docker containers because the method and paths will vary depending on how nested you are, etc. It’s just an absolute nightmare to deal with all-around in that context.

    I’ll see if we have some projects I can try out on it, but the majority of ours are like what I described above.