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
帖子
13
评论
613
加入于
3 yr. ago

I'm @froztbyte more or less everywhere that matters

  • flashbacks

    it's deeply upsetting how far that rotten idea has spread

  • oh absolutely no intention of listening to the dork, just had to share the suffering once I saw the tweet

  • I am extremely, extremely sickos.png for having all these weird little fucks find out that all this nonsense is heavily subsidised by VCs

  • after that Flock shit that got announced recently, looks like garry tan is currently doing his damnedest to ensure people know he's absolutely full of it

    thread starts here, features bangers like this

    You're thinking Chinese surveillance

    US-based surveillance helps victims and prevents more victims

    "nooooo, we're the good kind of boot to have on your face! we're the boot from the same country as you!" says the boot in the rising fascist upswing

  • “Qnx is hard and expensive, I’m sure we could get a production quality thing out with the esp-idf arduino target!!~ You devs so like to blow things out of proportion”

    (while not an exact quote, extremely close to some shit I’ve heard from some people before)

  • really leaning into the pivot theme

  • imma hazard a guess and bet David doesn’t want to do nearly that much work

  • ran across this

    Kaminski told SiliconANGLE in an interview he was inspired to launch the company after seeing how long and difficult it was for medical technology firms to bring innovations to market.

    “Everything that’s meaningful is regulated,” Kaminski said. “I didn’t even comprehend how hard it could be.”

    “I could code that in a weekend” techbro meets decades-grown safety nets, is very surprised at complexity

    I haven’t dug deeper into their thing yet but some of the claims are a bit 🤨 too

  • You're willing to admit it, and I bet that a bunch of other folks are, too. I appreciate it.

    it’s been mentioned/addressed a few times around here over the weeks, and I recall discussing it with friends elsewhere too (esp. around things like the humanoid robot listicle site). certainly a minority opinion, feels like, but definitely talked about

    handily, the inverse is also true: it’s really telling (about the people) to watch what emplacement expectations some people have for humanoid bots. some real “nice when they wear their sign” shit

    (e: added the listicle site link; I also recall posting it on the stubsack here a while back, but not gonna try find that now)

  • heh fuck you’re right, I forgot about that

  • heh you may be right, they certainly do appear to be that flavour of delusional

  • a good post all over, and something that'd be a good thing if other people also introspected their use of these things in a similar manner. I get why they don't, ofc (good lord so many tired people), but it'd be nice

    now every time you use the Google Assistant, you get a popup that compels you to switch to Gemini.

    this is one of the things that is so very mindbending for me. to me it is so very obvious that: because all of these things are a service, because the shape of service is subject to the whims of the organisation creating it, because that organisation will always feel the pressure of "market forces" (or in the more recent case, product desperation), these things will almost every[0] damn time result in some shit that an end-user cannot control. and yet that same person ends up reliant and expectant on these things, only for it to be ripped from their grasp, in a manner that may well amount to it being "murdered" in front of them

    the state of where we're at with "service-shape" as it pertains to sociological impact is just very not good atm :|

    [0] - I hesitate to say "always" here, but it's more or less what I mean

  • Me, 17 days ago

    this really isn't a hard guess

    You want my take

    probably not

    anyone who gets hired for slop cleanup should try to squeeze as much cash out their clients as much as possible

    "people should try to get paid well"? that's your whole take? really? you thought this was worthwhile posting? not, maybe, spitballing ideas for how people should get paid well? some advice on how to negotiate with clients who are quite likely to be pennypinching types (evidenced by them trying to get as much as possible for free)? none of that, just more fluff? okay then

  • noted for advancements in cryptography, and “stayed impartial” (iirc not quite defending, but also not acknowledging nor distancing) when the jacob appelbaum shit hit wider knowledge

    probably about all you need to know in a nutshell

    the most recent shit before this when I recall seeing his name pop up was when he was causing slapfight around Kyber (ML-KEM) in the cryptography spaces, but I don’t have links at hand

  • ah yes, that great mark of certainty and product security, when you have to unleash pitbulls to patrol the completely not dangerous park that everyone can totally feel at ease in

    (and of course I bet the damn play is a resource exhaustion attack on critics, isn’t it)

  • also from a number of devs who went borderline malicious compliance in "adopting tdd/testing" but didn't really grok the assignment

  • best advice I'd have for you is continuing with python is fine but

    1. find a good mentor
    2. read a lot of sourcecode (both good and bad), reason through stuff, try to understand the decisionmaking behind things

    on the good, you could read code by people like glyph, hynek, projects like twisted. they have years of experience, high mark of quality, care for their work, and also do a lot of teaching

    on the bad, you could read something like the code to home assistant (and/or esphome), or bits of calibre code (and calibre plugin code). I will say that these are not bad intentionally, but bad out of "someone inexperienced trying their best". it ends up creating a very particular kind of other thing.

    you can, and should, learn from both

    µPython is a bit of a special beast in that it's juuuust close enough (and handy enough) that it can trip you up, because there's some notable significant differences that if you spend all your effort in it first you might pick up bad habits that don't apply elsewhere (off the top of my head, some of the applicable: scoping, some arg-handling semantics, stack stuff)

    other bit of advice: remember, it's all just code. especially when you deal with libraries, if some error is coming out of a thing your first instinct may be to try ask the internet but you could also dive into the library - follow the callpath, figure out what's what, see if you can figure the problem out yourself. it's often not too hard, and it gives you some good practice of code reading and reasoning