Landie

i feel so bad for all these malicious vrchat 3rd party vibe slop software i've been seeing lately just to connect simple things ill do my part and add OSC support to my app so you can just use whatever my app supports, in vrchat so thats twitch, youtube, pishock, home-assistant, whatever tf

games with prevalent modding communities i see are getting hit the hardest with the slop trend

electron feels like the coolest technology ever when your use case actually makes full regular use of running an environment like that, but what most people use it for is definitely just a shortcut to making a low maintenance cross platform desktop app and dont even try to optimize it...

for the record, low maintenance cross platform desktop app is a valid use case, but its often done so poorly that its just a stain on the tech as a whole and also you.. probably should use something else...

I think one of the simplest improvements anyone can make to UX design is to remove any redundant prompts For example: If a window will always have a close button in the corner, it makes no sense to have another button that verbatim does the same thing.

This is such an unbelievable slap in the face to developers like me who single-handedly make Twitch one of the most interactive and innovative spaces with ease-of-use tools that allows streamers to make anything their minds can think of, all while understanding how it all works. I have no words. 💔

If you want to vote against this, please check out the UserVoice topic.

upset that the router i got uses a broadcom chip and i cant get OpenWrt on it, so im using a pi 5 i have laying around to turn into a router and use the other router as an access point instead networking is cool

I sincerely apologize for not being more public about my app and only spilling details to my patrons. But I have several fears. I want the first impression, to be the *right* impression. When it gets announced, I want people to engage with it somehow immediately, with mailing list, or some beta.

I want people to know that a single person is behind the app, and that person is approachable. The language of the app is personal, and often in the first person, like "I broke something" versus "Something went wrong" popups I own my mistakes, and you can know I own them

I sincerely apologize for not being more public about my app and only spilling details to my patrons. But I have several fears. I want the first impression, to be the *right* impression. When it gets announced, I want people to engage with it somehow immediately, with mailing list, or some beta.

I want the most important part of the app to be the most polished, which is the act of creating automations, and adding extendable features with a plugin module system.

I sincerely apologize for not being more public about my app and only spilling details to my patrons. But I have several fears. I want the first impression, to be the *right* impression. When it gets announced, I want people to engage with it somehow immediately, with mailing list, or some beta.

just learned that godot actually supports upgrading a tcp connection to be WebSocket compliant i like this approach more than other engines having a dedicated WebSocket server creation method; better illustrates how WebSocket servers ACTUALLY work and doesn't shy away from showing that to the user!

sorry for weird variable names, its how i make sure a dedicated thread only screws around with variables it's allowed to mess with

The approach ill take for some educational content on my app is to show how to build a topic on your own to a basic, extensible level, then, at the end, show a plugin version that simplifies most stuff you saw; You'll know what is being simplified and can make an informed decision on what to rely on

I want to do this is because its an app that encourages you to make stuff for yourself to further your knowledge to build bigger and better things, but also, it has the opportunity to use plugins to make your life easier on that front. Its important to teach people where to use their time methinks

got a complaint recently that ive made "hating AI" my "personality" when a topic completely overtakes a hobby and people automatically assume everyone engaging with said hobby inherits said topic, I need to be vocal on my stance, otherwise people will assume. so realistically its ai bro's fault.

im *personally* too verbose. clean, "perfect" code usually is concise and to the point, self documenting. I just have a lot of fluff because I have a lot of redundant checks and like to return "result" values as a tuple and dont use fancy unwrapping, just if statements. easier to read for everyone.

got a complaint recently that ive made "hating AI" my "personality" when a topic completely overtakes a hobby and people automatically assume everyone engaging with said hobby inherits said topic, I need to be vocal on my stance, otherwise people will assume. so realistically its ai bro's fault.

im now stuck having to be perfect with my code or else im suspect. but not too perfect! otherwise that looks suspicious because im too verbose. proper grammar in comments? better look out buddy. Too many comments? ... ok actually yeah thats a major sign ngl but you get what I mean

got a complaint recently that ive made "hating AI" my "personality" when a topic completely overtakes a hobby and people automatically assume everyone engaging with said hobby inherits said topic, I need to be vocal on my stance, otherwise people will assume. so realistically its ai bro's fault.

should I tone down my complaints? should I not speak so often of it? I personally dont think so. I dont feel comfortable being quiet especially when its just getting worse and worse and im hearing things like "works on my machine is a sign of AI code" and "misaligned labels is vibeslop signs"

I think as a developer making an automation software its crucial that I dont give easy access for a user to abuse APIs because non-programmers can easily accidentally overwhelm improperly set-up services with just a couple drag and drop blocks and they wouldnt know any better

There also wasn't any resources to teach users how APIs work, how to follow their rules, and more. failure to adhere to those rules can result in getting locked out, having an application reported, or in more extreme cases, an IP ban

I think as a developer making an automation software its crucial that I dont give easy access for a user to abuse APIs because non-programmers can easily accidentally overwhelm improperly set-up services with just a couple drag and drop blocks and they wouldnt know any better