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

help-circle


  • Someone suggested I try Supermaven yesterday, it’s got some good benefits over competitors. It has a 300,000 token context length so it can send a very large amount of context for your completions, and it has an extremely fast API response time (usually less than 200ms) so completions appear near-instantly as you’re typing.

    It’s the first “copilot-like” tool I’ve used, and I’ve only been using it for a day, but so far I’m liking it. And I’ve already signed up for the $10/month pro plan.


  • We use NoMachine at work too, for WFH users’ remote access to internal servers and virtual desktops. It’s a nice tidy solution, it was forked from NX library from the X2GO project about 10 years ago and went commercial, they used the commercial money to continue to develop the technology.

    Given it was forked from NX/X2GO it definitely works better on Xorg than Wayland, it seems like Wayland support was added as an afterthought bolted on.



  • Sounds like your friend is absolutely not the target audience for a linux-based operating system. If he wants to play Windows games and use software designed for Windows, then he should be using a Windows OS. Anything else would be providing a suboptimal experience for him.

    Personally, I’ve been using various Linux-based systems since 2004, as a software developer I use a lot of command-line utilities, and many tools and applications designed for Linux. If I were using predominantly tools and applications designed for Windows, then I would be using Windows. No need to make life more difficult for yourself and others.







  • Oh, I remember having to use Yocto when I started experimenting with the BeagleBone Black SBC back in 2015. Yes I remember it being very hard to use. I remember I had need to rebuild the kernel to include a disabled kernel module. The cross compilation on my desktop PC didn’t work, so I had to build it on the BeagleBone. That was an awful process, it took about 6 hours.

    For anyone not familiar, the BeagleBone Black was an SBC that came out as competitor to the Raspberry Pi 2. The main difference was the BeagleBone used an open source design, based on a non-NDA CPU unlike the RPI, so it meant they published full kernel sources. But in my experiments I found the BeagleBone CPU was much slower than the RPI, and it’s graphics hardware was almost non-existent compared to RPIs integrated graphics.


  • flubba86@lemmy.worldtoProgrammer Humor@lemmy.mlAnd don't forget RTFM
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    4 months ago

    Actually this is the biggest hurdle in leaning how to code. You can blame the huge numbers of “learn to code in 24 hours” articles and videos online and the the influx of “5 day bootcamp” courses. Its like teaching someone the basics of how to drive a car but never teaching them the road rules and never taking them on the road.

    A better analogy might be learning a foreign language. It’s like teaching someone all the words in Spanish, but never putting them together in a conversation.

    I’d argue that if you say “I know how to code, I know what variables are and how to print text to the console, how do I make an app?” Then actually you don’t know how to code. You might know the basics of a programming language, and that is the first step in learning coding, but there are many steps after that.

    I identified this gap a few years ago after seeing a couple of my friends (one finished a boot camp, and one finished a software development major at Uni) both were in this same situation. I determined there is a big gap between “knowing a programming language” and “knowing how to make software”. It’s like going from “I know how to write words” to “I know how to write a novel”. It’s not something that comes easy. It’s something that can take time (often years) to get good at. This is the reason you see requirements like “3 years software development experience” on entry level programmer jobs. The number of people in your situation is incredibly high. The coding bootcamps churn them out by the hundreds every month.

    A couple of years ago when I was between jobs, I created a Gumtree ad advertising “post-bootcamp” courses, that aimed at bridging this gap. It was a series of private 1on1 lessons aimed at teaching someone to go from “knowing how to code” to being “software developer” job ready. Lots of people have many different learning styles and different paths they took to this point. The key is focussing not on the giving them the missing information, but teaching the person how to identify what steps are missing and how to find resources to learn them (because that’s the real missing knowledge wink).

    Unfortunately I found some people didn’t want to learn how to learn for themselves, and just wanted me to hand them the “secret missing parts” on a platter.



  • We use containers in our work whenever possible, to reduce the problems caused by different development environments and deployment environments. And as a Linux user I embrace the idea (Linux dev containers for every project!) but it has unfortunately made things harder for our Windows developers. Docker on windows is a difficult to get right. Throw Docker-Desktop and WSL2 in the mix, you have a nightmare. They all come to me with “why isn’t my Docker environment working?!”.