unmagical

u/unmagical@lemmy.ml
3 posts · 2.2k comments

Recent posts

Recent comments

Have a look at Open IPC and Yi-hack (link is to one specific family of their cameras, but there are hacks available for other non-allwinmer models too).

I believe you can also hook up a raspberry pi (with a camera module) to Motion Eye wirelessly.

The easiest thing for security (though not necessarily own source) would be to find a WiFi cam that offers offline or local access and confining it to it's own subnet that doesn't have access to the internet. I think you can do this with reolinks, but double check.

on Choices · c/lemmyshitpost · 16 pts · 2d

I think I've eaten at McDs like once in the last 5 years or so, but I'd still opt for the year of it in the knowledge that I don't have to use it. Could feed a lot of homeless people at least.

  • Learn git now. Use it for every project.
  • Focus on the flow of your code, knowing perfect syntax is great but it's the tool we use to actually accomplish the thing we're trying to do and we've got tools and resources to help you master syntax later.
  • Algorithms are great, but you likely won't need to have therm all memorized when doing a job (an interview might be different). Learn what an algorithm is, practice implementing a few, learn the general idea of what a bunch of different algorithms can offer for different situations.
  • You'll always be able to look shit up on the job, but the less stuff you have to look up the more efficient you'll be.
  • Start and finish projects. Like fully finish, push something useful to npm or NuGet, stand up a website with a domain you control.
  • Don't just focus on one area at the start. Learn web stuff, but also at least one native language. Maybe get a microcontroller and set up a project where you can control something in the real world from a web interface.
  • Understand the use cases and differences of various languages and technologies. Why use go vs rust? Why use Java vs C#?
  • Learn the different styles of coding practices. Your codebase will be a mix of a bunch of different ones cause you'll end up writing what makes sense at the time, but knowing different styles will help you know what actually does make sense at different times
  • Avoid AI as you're learning. Your knowledge of code and it's underlying principals will allow you to understand when the AI is wrong--and it will be wrong. It's important to grow those fundamentals before reaching for a tool whose mistakes will be your responsibility.
  • Use Linux
    • I'd recommend using a high level OS like Debian or Fedora for a bit as you familiarize yourself with how to use Linux then try an arch install (not through any GUI) to learn how Linux actually operates.
  • Buy Unix socks
on 3.5 is here to stay · c/neinhole · 1 pts · 3d

Okay. That doesn’t mean your graphic makes physical sense. Either its perspective or the construction of the machine it portrays are wildly wrong.

on 3.5 is here to stay · c/neinhole · 1 pts · 3d

Is that 5.25 floppy the same width as the 3.5" or is the guillotine just drastically out of square rendering the 3.5 to fall haphazardly and unguided?

Genuinely can't tell if you were taking my comment in Shitty Ask Lemmy seriously or just responding in kind to the caricature I had fabricated based upon my past interactions with evangelicals.

on Beast game · c/microblogmemes · 132 pts · 3d

Dude literally watched Squid Game and said that shit would be better if it were real then set out and did it.