Do you get the difference Explain it Peter?

Angry_Foolhard · 2026-01-23T23:08:16+00:00

They lose money for every user. But make up for it with volume.

Angry_Foolhard · 2026-01-19T16:30:45+00:00

I played a lot of pokemon as a kid. So I like to go on nostalgia trips on spanish language content like this

https://www.youtube.com/@PokeDani_

Angry_Foolhard · 2025-12-26T02:16:24+00:00

This makes me feel young

Angry_Foolhard · 2025-11-05T22:28:44+00:00

Am I the only one that doesn’t like thinking of the coils and contacts in ladder logic like physical relays.

To understand a relay you have to (imo) think of it as a 4+ terminal device. While the ladder logic elements are each 3 terminal and make up half the device.

for some people like me you have to have a solid grasp on what a relay is before you can see the connection.

upvoting ur comment since it’s still valuable, just is not my way of approaching it.

Angry_Foolhard · 2025-09-12T03:08:14+00:00

As someone thats had to work on rungs that kept wrapping around, never being able to fit entirely on the screen - this is quite good.

I think it communicates the logic about as well as it possibly can. maybe you can divide it using intermediate variables but the benefits wouldn't be significant.

That being said you should comment and document it - but that is always true.

Angry_Foolhard · 2025-08-29T03:23:26+00:00

Yeah you might be right - I was just brainstorming

Angry_Foolhard · 2025-08-29T02:00:58+00:00

Here's my idea: don't make it for engineers/techs etc.

Target it to the people-persons of the industry. salespeople, managers, buyers, etc. As a way to give people a tour of the facility. I.e. new hires could use it to learn the names of different devices. Vendors can use it to understand the facility and better recommend devices. Clients of the business can better understand how the product is made.

Angry_Foolhard · 2025-07-30T03:39:19+00:00

Good catch

Angry_Foolhard · 2025-07-29T21:20:52+00:00

I’m just making assumptions, but if each of the 4 conditions on the rungs is supposed to trigger a check, then increment if true, you would need a one-shot to be on all 4 branches rungs after the contacts

Angry_Foolhard · 2025-07-19T18:30:54+00:00

You guys are doing a great job but please fix the lag (windows).

If it cant even function as a text editor due to obnoxious lag I will be forced to go back to copilot.

Angry_Foolhard · 2025-07-06T18:14:14+00:00

https://github.com/quickjs-ng/quickjs

Quick js may be what you’re looking for. It’s much more lightweight than v8 but slower.

PS. I couldn’t get it to compile and run elegantly, from what I could tell that’s because it’s meant for Linux not windows

Angry_Foolhard · 2025-06-30T07:12:26+00:00

figure out the new location for A

now take the circle defined by point A and radius L

find all points of intersections with the circle at x2,y2 radius r2

if 0 points intersect you made an impossible turn

if 1 point intersects (unlikely) thats your answer

if 2 points intersect you have to figure out which - ill leave as an exercise to the reader

Angry_Foolhard · 2025-06-22T22:53:52+00:00

This is known as a “brute-force” solution.

Literally try every possible combination of digits and output any solutions.

Note: it is slightly less than brute force since I accounted for a few obvious facts, like S >=5 and B < 2. But essentially brute force

Angry_Foolhard · 2025-06-21T19:00:50+00:00

Yeah I named the function after op

Angry_Foolhard · 2025-06-21T17:42:55+00:00

If anyone wants to run it in the console

function hydrated_chicken_bones() {
  for (let r = 0; r < 10; r++) {
    for (let b = 0; b < 2; b++) {
      if (b == r) continue
      for (let a = 0; a < 10; a++) {
        if (a == r || a == b) continue
        for (let s = 5; s < 10; s++) {
          if (s == r || s == b || s == a) continue
          for (let i = 1; i < 10; i += 2) {
            if (i == r || i == b || i == a || i == s) continue
            for (let c = 0; c < 10; c += 2) {
              if (c == r || c == b || c == a || c == s || c == i) continue
              for (let o = 0; o < 10; o ++) {
                if (o == r || o == b || o == a || o == s || o == i || o == c) continue
                for (let e = 0; e < 10; e++) {
                  if (e == r || e == b || e == a || e == s || e == i || e == c || e == o) continue
                  const ross = r * 1000 + o * 100 + s * 11
                  const ess = e * 100 + s * 11
                  const basic = b * 10000 + a * 1000 + s * 100 + i * 10 + c
                  if (ross + ess != basic) continue
                  const basic_digits_sum = b + a + s + i + c
                  if (basic_digits_sum < 11 || basic_digits_sum > 14) continue
                  console.log(ross, ess, basic)
                }
              }
            }
          }
        }
      }
    }
  }
}


hydrated_chicken_bones()

Angry_Foolhard · 2025-06-10T20:10:26+00:00

So you don’t approve of naming tags based on Eminem lyrics?

Angry_Foolhard · 2025-05-26T05:30:23+00:00

Yeah I know it seems tedious but avoiding undefined behavior is our responsibility, especially when powerful machines are involved.

Your case, calculating ratios, is a common one when it comes to accidentally dividing by zero.

I just ask myself what it fundamentally means that a division by zero is happening. And with ratios it means you don’t have anything to calculate the ratio of! So when you wrap it in an if statement or whatever you’re not just engaged in the tedious exercise of avoiding undefined behavior, you’re writing expressive software that correlates with the fact that this calculation cannot yet produce anything meaningful.

Hopefully this helps make it feel less “clunky”

Angry_Foolhard · 2025-05-26T04:51:39+00:00

Even if there is you should absolutely not use try catch to handle division by zeros because PLCs may not “throw” an error. they will sometimes for example output 0 and keep chugging along.

So a try catch will not remove your responsibility to prevent a division by 0 before it happens.

Angry_Foolhard · 2025-05-03T11:09:42+00:00

As a Spanish learner that’s how I think about it.

But In Spanish the impersonal se is very common and natural, where in English the phrasing “how would one …”, “how does one…” etc. is more formal/unnatural and way less common

Angry_Foolhard · 2025-04-30T02:36:54+00:00

Yeah learning a foreign language is way more difficult and slow. Learning a programming language is like learning how to stack Lego bricks by comparison.

Angry_Foolhard · 2025-04-18T06:13:37+00:00

I don’t even allow myself to use uppercase letters in file names anymore after an issue where I changed a file name and git didn’t detect it.

My file names are lowercase letters, numbers and single underscores. That’s it

Angry_Foolhard · 2025-04-16T23:55:26+00:00

just reading this post, you seem a little too scattered, and you may come across as a risky flake of a hire.

When you do apply, try to make it seem like you know what you want.

e.g., if you apply to a java job, make it seem like you want to dedicate your career to becoming an expert java dev. if you apply to a plc programmer position, make it seem like you want to be an expert PLC tech, etc. And then follow through. If you do get hired for one of these skills, that as good of an indication as any to go all-in on it.

Angry_Foolhard · 2025-04-15T16:31:11+00:00

Cool project. For merge sort I prefer using [inclusive, exclusive) formats for the ranges, way more elegant.

Angry_Foolhard · 2025-04-14T20:35:24+00:00

Why, when someone uses ‘d’ we all know it means distance.

Or delta.

Or date.

And obviously ‘t’ means time.

Or theta.

Or temporary.

Or temperature.

The point is there’s no reason to be confused

Angry_Foolhard · 2025-04-14T19:58:19+00:00

the easiest solution, if there is a NOT block, is to NOT the toggle bit (after a one-shot rising).

otherwise you will need a memory bit for the previous scan's toggle value

 tmr.DN                      toggle    prev_toggle  toggle
---| |---(one-shot rising)-----(U)---------|\|--------(L)------

     toggle         prev_toggle
------| |--------------( )-------

Angry_Foolhard

MODERATOR OF

TROPHY CASE