home.social

Search

537 results for “nurkiewicz”

  1. @nurkiewicz and merged. And the follow-up request to clean up now unused zig files was created. And closed by #AI. As ai #slop. Ironic.

  2. @nurkiewicz and merged. And the follow-up request to clean up now unused zig files was created. And closed by #AI. As ai #slop. Ironic.

  3. @nurkiewicz and merged. And the follow-up request to clean up now unused zig files was created. And closed by #AI. As ai #slop. Ironic.

  4. @nurkiewicz and merged. And the follow-up request to clean up now unused zig files was created. And closed by #AI. As ai #slop. Ironic.

  5. @nurkiewicz and merged. And the follow-up request to clean up now unused zig files was created. And closed by #AI. As ai #slop. Ironic.

  6. @nurkiewicz
    Right, I now see why/ how some jobs posted in LI are from the completely wrong company...
    (I inferred a recruiter is doing both jobs, but didn't shift login, so the post has wrong source/ account).
    Your observation implies the recruiter would be completely doing professional practice.

  7. Back in 2014 I had a talk on the very first conference. One of my slides was joking that all of these lines are equivalent, except one, which doesn't compile. I have no idea which one was it ;-)

    The last time I used full-time was almost a decade ago | nurkiewicz.github.io/talks/201

  8. I'm speaking at about building resilient services in 1 hour. Check out the slides already! nurkiewicz.com/slides/resilien

  9. @infosec812 Actually simplified WebSockets significantly. E.g. here's a complete rudimentary chat that receives a message over web socket and broadcasts to everyone else: github.com/nurkiewicz/reactor-. Maybe 10 lines of real code.

  10. @nurkiewicz SSE is easier in Java with the typical JAX-RS/Spring APIs... WebSockets are a dream if you use #VertX. I think the problem is not the technology, but the implementation in Java being overly complex.

  11. @glaforge @rdmueller are particularly fun for experimenting because they don't require authorization. I tried a global stream of posts and works great! mastodon.social/@nurkiewicz/10

  12. @[email protected]: "Dziś w Better Software Design rozmowa z @nurkiewicz na temat programowania reaktywnego. Jak działa ten paradygmat, w czym pomaga, a kiedy przyniesie więcej problemów niż korzyści - o tym wszystkim (i nie tylko) można posłuchać w odcinku BSD 44"

    bettersoftwaredesign.pl/episod

    #RxJava #Reactor #Reactive #Java #RxJS

  13. @[email protected]: "Dziś w Better Software Design rozmowa z @nurkiewicz na temat programowania reaktywnego. Jak działa ten paradygmat, w czym pomaga, a kiedy przyniesie więcej problemów niż korzyści - o tym wszystkim (i nie tylko) można posłuchać w odcinku BSD 44"

    bettersoftwaredesign.pl/episod

    #RxJava #Reactor #Reactive #Java #RxJS

  14. @[email protected]: "Dziś w Better Software Design rozmowa z @nurkiewicz na temat programowania reaktywnego. Jak działa ten paradygmat, w czym pomaga, a kiedy przyniesie więcej problemów niż korzyści - o tym wszystkim (i nie tylko) można posłuchać w odcinku BSD 44"

    bettersoftwaredesign.pl/episod

    #RxJava #Reactor #Reactive #Java #RxJS

  15. @[email protected]: "Dziś w Better Software Design rozmowa z @nurkiewicz na temat programowania reaktywnego. Jak działa ten paradygmat, w czym pomaga, a kiedy przyniesie więcej problemów niż korzyści - o tym wszystkim (i nie tylko) można posłuchać w odcinku BSD 44"

    bettersoftwaredesign.pl/episod

    #RxJava #Reactor #Reactive #Java #RxJS

  16. @[email protected]: "Dziś w Better Software Design rozmowa z @nurkiewicz na temat programowania reaktywnego. Jak działa ten paradygmat, w czym pomaga, a kiedy przyniesie więcej problemów niż korzyści - o tym wszystkim (i nie tylko) można posłuchać w odcinku BSD 44"

    bettersoftwaredesign.pl/episod

    #RxJava #Reactor #Reactive #Java #RxJS

  17. RE: fosstodon.org/@nurkiewicz/1164

    It’s all about the money and it always was. As AI vendors start charging what it actually costs instead of burning VC, this is going to change the story from „we’re gonna fire you for not using enough AI“ to „pleeeease use it only when it really helps“. Turns out, this is something, that well trained engineers can actually do.

    #ai #anthropic #tokenmaxxing #swdev #programming

  18. RE: fosstodon.org/@nurkiewicz/1164

    It’s all about the money and it always was. As AI vendors start charging what it actually costs instead of burning VC, this is going to change the story from „we’re gonna fire you for not using enough AI“ to „pleeeease use it only when it really helps“. Turns out, this is something, that well trained engineers can actually do.

    #ai #anthropic #tokenmaxxing #swdev #programming

  19. RE: fosstodon.org/@nurkiewicz/1164

    It’s all about the money and it always was. As AI vendors start charging what it actually costs instead of burning VC, this is going to change the story from „we’re gonna fire you for not using enough AI“ to „pleeeease use it only when it really helps“. Turns out, this is something, that well trained engineers can actually do.

    #ai #anthropic #tokenmaxxing #swdev #programming

  20. RE: fosstodon.org/@nurkiewicz/1164

    It’s all about the money and it always was. As AI vendors start charging what it actually costs instead of burning VC, this is going to change the story from „we’re gonna fire you for not using enough AI“ to „pleeeease use it only when it really helps“. Turns out, this is something, that well trained engineers can actually do.

    #ai #anthropic #tokenmaxxing #swdev #programming

  21. RE: fosstodon.org/@nurkiewicz/1164

    It’s all about the money and it always was. As AI vendors start charging what it actually costs instead of burning VC, this is going to change the story from „we’re gonna fire you for not using enough AI“ to „pleeeease use it only when it really helps“. Turns out, this is something, that well trained engineers can actually do.

    #ai #anthropic #tokenmaxxing #swdev #programming

  22. I think we don't appreciate how good modern video encoding is. 2 hour long, 4K video at 60 fps would take roughly 10 TiB if each frame was encoded individually and with no compression (BMP). H.264 needs 3 orders of magnitude less (10 GiB-ish)

  23. Let's take the best from row-based and columnar databases and store data diagonally

  24. TIL every #YouTube channel has a proper, built-in, well hidden #RSS feed! Here's an example for 3Blue1Brown channel: youtube.com/feeds/videos.xml?c. Just look for `videos.xml` in the HTML of channels home page

  25. TIL every channel has a proper, built-in, well hidden feed! Here's an example for 3Blue1Brown channel: youtube.com/feeds/videos.xml?c. Just look for `videos.xml` in the HTML of channels home page

  26. TIL every #YouTube channel has a proper, built-in, well hidden #RSS feed! Here's an example for 3Blue1Brown channel: youtube.com/feeds/videos.xml?c. Just look for `videos.xml` in the HTML of channels home page

  27. TIL every #YouTube channel has a proper, built-in, well hidden #RSS feed! Here's an example for 3Blue1Brown channel: youtube.com/feeds/videos.xml?c. Just look for `videos.xml` in the HTML of channels home page

  28. TIL every #YouTube channel has a proper, built-in, well hidden #RSS feed! Here's an example for 3Blue1Brown channel: youtube.com/feeds/videos.xml?c. Just look for `videos.xml` in the HTML of channels home page

  29. /#neovim scrolling:
    - top/bottom: gg/G
    - page up/page down: Ctrl+B/Ctrl+F (or... PgUp/PgDn, duh!)
    - scroll w/o moving cursor: Ctrl+E/Ctrl+Y
    - scroll to put current line at top/middle/bottom: zt/zz/zb
    - move cursor to top/middle/bottom of screen: H/M/L (note: H and L are remapped by )

  30. #vim/#neovim scrolling:
    - top/bottom: gg/G
    - page up/page down: Ctrl+B/Ctrl+F (or... PgUp/PgDn, duh!)
    - scroll w/o moving cursor: Ctrl+E/Ctrl+Y
    - scroll to put current line at top/middle/bottom: zt/zz/zb
    - move cursor to top/middle/bottom of screen: H/M/L (note: H and L are remapped by #LazyVim)