Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)F
Posts
2
Comments
1231
Joined
3 yr. ago

  • If you find yourself reaching for this feature it probably means your Bash script has reached the level of complexity where you should absolutely not be using Bash. Use a real programming language instead.

  • I think the use of the term junior and senior is a bit confusing because it conflates age and skill. I would say most people use it to talk about skill, because we're talking job titles here.

    While age and skill are certainly linked, I have known several junior engineers well over 50 (don't hire these people!), and also some extremely skilled engineers in their very early 20s. The latter hadn't yet earned the "senior" job title but that's just because they didn't know they deserved it yet.

    So yeah I do think junior (skill) programmers are pretty screwed - AI is already at least on par with the junior skill level people I've worked with. But I don't think that means young people are screwed, as long as you are good at your job.

    For now anyway. Who knows how good AI will be in 5 years. We might all be out of a job.

  • Not sure how that's relevant but good for you.

  • I've spoken to two friends recently, who are just normal (but highly skilled) devs, and they both said they don't write code any more.

    That's about as random a sample as I can get. These aren't Anthropic employees on Twitter. Just normal people.

    So if you think AI isn't revolutionising how software is made then I'm afraid you're in the "it's just Apple fanboys buying the iPhone; Nokia forever!" stage of denial.

  • Yes. If they train AI from your code? No, but the legality of that is yet to be settled and definitely leaning towards "it's fine".

  • Find me a repo on GitHub with a license that disallows cloning it. I'll wait.

  • So have they. They filter by license - see my other comment.

  • but it may be violation of licenses

    They excluded code with non-permissive licenses apparently:

    Each file is labelled permissive (at least one permissive license detected, no conflicting non-permissive license), no_license (no licenses detected, or only non-license legal texts such as CLAs), or non_permissive. The permissive allowlist follows the Blue Oak Council list plus licenses categorized as Permissive or Public Domain by ScanCode. Files classified as non_permissive are excluded from both released datasets.

    also, if it has personal information on it, that’s probably illegal under the GDPR.

    It's all public so I would be extremely surprised if that were the case.

  • I'm pretty sure they just cloned the repos. That's how GitHub is designed to work. Have you never cloned a repo from GitHub?

  • don’t steal the repositories

    How is this remotely stealing?

  • I mean they'd have been ok with it because tech bros were the ones automating other people out of jobs and never thought it would come for theirs.

    The level of AI we have now was impossible science fiction a decade ago.

  • This specifically isn't illegal though. They've only scraped public repos.

  • I could use two &mut [T] values, built with split_at_mut, but this is unwieldy.

    This is likely to be the best option. You could wrap it in a nice interface that provides normal indexing but panics if you index the forbidden element. AI will be able to easily write that code for you.

  • and even if one has to do such a refactoring what is the point of using YAML at all ?

    It allows the CI engine to determine which jobs to start, what their steps are etc.

    To be fair I have worked on one project that had very complex CI and we almost decided to generate the CI graph procedurally with a Python script (Gitlab supports this, somewhat awkwardly). But in the end we decided it wouldn't be worth the overhead of writing, maintaining and learning a whole new CI system on top of Gitlab's CI.

  • You can (and should!) do exactly the same with "traditional" GitHub Actions style YAML.

    Avoid putting commands in the YAML - put those in separate scripts and call them from the YAML. The YAML should only be used for things that can't be done from scripts (e.g. job matrices, uploading artifacts, reporting status etc.)

  • Seems reasonable but good fucking luck enforcing that.

    IMO they should instead simply charge cost price for hosting. It can't be much surely?

  • I totally agree about story points being bollocks. Their supposed justification is that you can measure velocity by seeing how many story points you do per month, but that only works if there's no feedback from velocity to story point estimation which is obviously not the case.

    So in practice they just become a stupid proxy for time. "1 story point is an hour right?"

    The Fibonacci thing makes some sense to me though - it is a way of suggesting that bigger estimates are less accurate.

    Of course it would be much better if you could actually put an accuracy directly into Jira or whatever (e.g. 10-30 hours), but that would apparently be way too complicated. You could also get that data fairly nicely from planning poker (which I also think is pretty good, but you throw away all the information about uncertainty that you just spent ages discovering!)

  • I really hope they don't copy how Git does submodules and LFS. They're both pretty terrible.

  • Well I guess not everyone learns at the same rate.