Hacker Newsnew | past | comments | ask | show | jobs | submit | ksajh's commentslogin

Being around and earning billions does not mean they're producing appropriate value


Its more about concerns about Airlines using video to micro-manage pilots. I too would hate it if my manager was watching my every move while working so I can empathize.


that could be easily solved though. is the data in the black box being analyzed after each flight by the employer ?


Sandwich


Not hotdog


> I think it's always a good thing to have a polyculture of dev tools.

What are your reasons?


Some ideas that come to mind:

  - Concentration of power/attention/market share/etc. can lead to abuse
  - Competing ecosystems push each to get better
  - Different tools can be good at solving different problems (e.g. different LLMs may be good as solving different tasks)
  - Allows people to use tools they're more comfortable with (e.g. worked at one company where everyone was forced to use vim, needless to say I didn't want to stay there long)


Writing prompts is much simpler than image analysis plus they make a AI test framework thingy


class Animal {

Circle circles_[13];

}


You also need to encode the painted areas somehow. They are not only intersections on K shapes, but sometimes exclusions as well (like (A^B)/C). Two ways come to mind:

(1) Listing closed curves by vertices. Each vertex of a painted area is an intersection of two or more circles, and delimits a section of a circle. So the section of circles that enclose a circle can be encoded each by the union of:

(1.1) A circle (index); (1.2) A 2nd circle (index) that intersects the 1st on a first point; (1.3) A bit identifying the (first) intersection (because there may be 2 possible); (1.4) A 3rd circle (index) that intersects the 1st on a second point; (1.5) A bit identifying the (second) intersection.

Note the base circle would be the first intersection of a subsequent section of this closed curve, and the 3rd circle would be the subsequent base circle. So 1/2/3 won't be necessary for subsequent curves. So only (K+2) indices + (K+1) bits are necessary for this encoding.

Total ~K log2(K)+K bits. I hypothesize (left to the reader :)) a closed curve should contain at most 2x13 points. There can be at most 2^13 distinct regions however, so each figure (Animal) can be encoded with less than that many curves per figure. So each figure (Animal) can be encoded with less than 2^13 x 26x(5+1) bits =~ 1.3Mbit.

But that's mostly pathological cases, if each Animal must be a fully connected area, then that might reduce (hypothesis above) to at most only 26x(5+1) bits = 156 bits, or 20 bytes!

I left out a problem which area shapes encoded within each other (like eyes). In that case you need at most another 156 bits per inner cutout shape.

(2) Alternatively, you could use boolean operations to encode each shape. Also left as a fun problem :)


  interface Animal {
    Circle[13] circles();

    // Leftover from Intro to CS, remember to remove
    void make_sound();
  }


Step 1: Read and understand the article


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: