Search
93 results for “codingcoyote”
-
Fanatical is doing a #charitybundle called the "War Chikd Charity Bundle 2025"
Even if just one of the games fits your library, consider helping out.
https://www.fanatical.com/en/bundle/war-child-charity-bundle-2025
-
#SecureCodeReview always fills me with either disappointment or excitement. It's a good exercise reading someone else's code, and trying to best them in a match of wits (by finding a missed security issue). But occasionally I see sloppy code that is clearly LLM regurgitated #copypasta that I feel a little sick.
Just caught a low risk Path Traversal vulnerability that has been in there for years and we missed it the last time this area was reviewed. 😎
-
I saw a pattern in #ReactJS today that made my heart hurt. A prop called `show` is passed in to tell the component whether or not to render.
The problem is, the render function of the component still runs on every render of the parent even when no e of the work is necessary. A better pattern is to define your condition and then use `&&` to avoid rendering it at all.
The reasoning behind it appears to have been familiarity for devs who came from #WinForms when we started this project.
-
I started the process of setting up dependency injection in a legacy enterprise app to be able to unit test it.
I've not had to do much with #moq before, but it's fairly intuitive once it clicks. For #arcaneSpaghetti written by wizards of old, you can assert that a specific mocked function was called once with a specific set of arguments, and then confirm it hasn't been called at all with others.
Found 11 distinct and very old bugs from these runs.
-
A #greybeard gave me some #careeradvice while we were working late on security reviews that is some of the best advice I've ever heard.
He told me to focus on retirement as early as possible. Pay off debt, and put back just enough investment that I can quit my job and work for something like a nonprofit or open source work that pays too little to cover the bills normally. Retirement isn't about not working. It's about doing something you actually care about.
-
Working on #adacompliance by trying to integrate a #texttospeech engine into #AOSP
#espeak has been deemed too low quality, and #sherpaTTS too slow. #RHVoice silently fails on our hardware, and I'm running out of options. Does @GrapheneOS have a TTS engine that would be commercially friendly enough for us to push it via OTA update? Or would anyone recommend one?
We work with a sensitive population and lack of a screen reader can make things even more difficult for some.
-
Working on #adacompliance by trying to integrate a #texttospeech engine into #AOSP
#espeak has been deemed too low quality, and #sherpaTTS too slow. #RHVoice silently fails on our hardware, and I'm running out of options. Does @GrapheneOS have a TTS engine that would be commercially friendly enough for us to push it via OTA update? Or would anyone recommend one?
We work with a sensitive population and lack of a screen reader can make things even more difficult for some.
-
Working on #adacompliance by trying to integrate a #texttospeech engine into #AOSP
#espeak has been deemed too low quality, and #sherpaTTS too slow. #RHVoice silently fails on our hardware, and I'm running out of options. Does @GrapheneOS have a TTS engine that would be commercially friendly enough for us to push it via OTA update? Or would anyone recommend one?
We work with a sensitive population and lack of a screen reader can make things even more difficult for some.
-
Working on #adacompliance by trying to integrate a #texttospeech engine into #AOSP
#espeak has been deemed too low quality, and #sherpaTTS too slow. #RHVoice silently fails on our hardware, and I'm running out of options. Does @GrapheneOS have a TTS engine that would be commercially friendly enough for us to push it via OTA update? Or would anyone recommend one?
We work with a sensitive population and lack of a screen reader can make things even more difficult for some.
-
Working on #adacompliance by trying to integrate a #texttospeech engine into #AOSP
#espeak has been deemed too low quality, and #sherpaTTS too slow. #RHVoice silently fails on our hardware, and I'm running out of options. Does @GrapheneOS have a TTS engine that would be commercially friendly enough for us to push it via OTA update? Or would anyone recommend one?
We work with a sensitive population and lack of a screen reader can make things even more difficult for some.
-
Someone updated #easyspeak to put on #GrapheneOS and saved me a ton of time. A custom #AOSP based OS I've been working with needed a TTS service for our proprietary app and the devices we have didn't have one. I need to make a few modifications so we don't have to configure it for every device we have, but #FOSS has saved me a significant amount of headache.
#SherpaTTS also worked well, but required too many resources and I didn't have enough vespene gas to justify building more pylons...
-
Friendly reminder that #html has attributes for inputs that can be used for things like on-screen keyboards and auto fill.
InputMode: https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/inputmode
And Type (for things like password): https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/input/password
If you develop #onscreenkeyboard software, please take these into account.
-
I just spent 4 hours writing #XUnit tests to prove a point. Constructive pedantry!
-
I opened a #codeberg repo in #gitkraken today and it gave me the choice to upgrade or close the repo because it detected it as a private or self hosted repository despite this being a somewhat well known GitHub alternative.
And so I'm looking for a new #git GUI for Linux. Going to try #relagit for a bit first
-
Why is it no college or code camp properly teaches debugging. It's not always an option, but it's a powerful option when it is.
Even more so if you have the ability to do live editing/hot reloading or #TimeTravelDebugging (really wish I could use this one at work).
-
I finished #skindeep today and wow! The final level was crazy but the boss fight was more of a wrap up cinematic. It's an excellent if a little out wonky #OpenSource #stealthgames entry.
-
Anyone who likes goofy #stealthgames should check out #SkinDeep
It's very fun and they released the source code to encourage more people to make games like this. Which also means it's probably insanely moddable now.
https://github.com/blendogames/SkinDeep
Send the devs some love and buy it on #steam (or wherever it's sold).
-
Today I learned some of my team has been using deploy scripts in #TeamCity to rewrite code for test sites and special builds.
I cannot stress enough how bad of a habit this is. If you are redirecting code, it should be done via configuration file changes not find/replace powershell scripts run on the codebase. This should be treated as dangerous since it could be used to circumvent security reviews if it happened on the production configuration.
-
If anyone has been using #NuGetDefense after my unexpected pause in development, know that a new release was pushed recently that fixes what is IMHO one of the most annoying bugs. The file access retry on the vulnerability data was failing before it entered the try/catch used to trigger the retry logic.
-
You may not care for their branding (or maybe they feature your waifu) but #GamerSupps has free shipping right now and it's my caffeine of choice. Cheaper and tastier than #monsterEnergy and AFAIK they aren't suing indie developers over the use of the word "monster".
This is what keeps me sane on the drive home after 14 hours of debugging spaghetti code and it's only $0.40 per drink.
-
Saw this on PCGamer, but the actual writeup on Hive systems is a great breakdown of why you need more complex passwords and longer passwords.
https://www.hivesystems.com/blog/are-your-passwords-in-the-green
-
I don't know when it happened, but the AI assistant in #JetBrains #Webstorm got really good at predicting what I'm about to write. The single-line auto-complete is accurate enough that I don't feel like I'm fighting the AI anymore and only have to make minor changes like I would with simpler auto completes I've dealt with before. Instead of just giving me the function name when I hit `.` it's also filling in the arguments I intend to use.
-
This includes chained #useEffect hooks in #ReactJS where each effect changes state that triggers the next useEffect. At least in those cases it tends to all happen in one place
-
For the sake of my sanity, please do not use a Rube Goldberg cartoon as your SRS. If I see one more button that writes to a database, so a timer can write to a different database, so another timer can trigger an update in a cache, so a service watching the cache can send a message to Even grid, so #eventgrid can send a message to a #signalR hub, so a signal r client can receive the event and call up to an API to get the data set by the button, I may lose my cool.
-
#Amazon has a handy button to change your language. And helpfully they've localized the names of each language so you can only tell what they are if you can read that language. Hablo Inglés y solo pequeño Español ... And I'm not fluent by any means.
The native spelling for that language should be the primary one displayed #badUI #badUX
-
#frontend and #fullstack devs: Be optimistic about API calls. Research has shown that as little as 100ms of delay is the time it takes for a user to go from perceiving they did something to perceiving they are waiting on something. And 250ms is enough for them to be upset about it.
I've seen too many instances where the UI doesn't update til the API call returns or a #signalr event comes back. If you can anticipate a response, let the UI assume it will succeed for the best UX that feels "magic"
-
Multi-language projects aren't terrible. Multi-framework projects are bearable, but multi-paradigm projects are not fun.
Working in what appeared to be a purely #functionalprogramming project and I find one feature where it's all suddenly #objectorientedprogramming. This too is only an issue while swapping between the two though (or trying to write reusable code).
-
I've been part of a team deploying signalR to handle millions of messages across thousands of devices and seeing it repeatedly fail to deliver the performance promises that it's marketed with.
All this seems to be because someone let themselves feel clever. That pride that makes you think you know better because of how complex a problem you solved is actually a red flag that your clever brain is overcomplicating a simple problem.
We all do it.
-
@mcc I have sent emails to some websites indicating what was wrong with their page and how to fix it. #HiDive (anime streaming platform), actually gave me 6 months of free service in response to one but said they were aware of the issue, and an overhaul of the affected components was already in the works.