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

As someone who has some familiarity with the people and processes, this response seems extremely off to me.

> Selection starts from age of 4

Care to share your sources for that? As far as I know most are self taught and get some further training in military.

> Boring.

It might be boring to some and might be extremely interesting for others. People who like solving puzzles and facing hard challenges usually like it. Of course, if your passion is building you wouldn't like it as you don't "build" something new.

> Usually a group of introverted young kids that look at their own shoes while talking to you, led by an extroverted young kid, that looks at your shoes while talking to you.

Have you met these people at all? Because it definitely sounds like you haven't and you just describe the typecast some movie would use.


> Care to share your sources for that?

I'm Israeli.

My children were attending/graduated/served kindergarten/school/army in Israel and I saw selection process as a parent.

My wife was a school teacher in Israel. She described to me some of the evaluation metrics she was supposed to submit every half a year over each and every pupil she had.

> Have you met these people at all?

I cannot confirm nor deny I met these people.


I have lots of friends who are ex-8200 (high levels of hightech are surprisingly full of them actually) and this is the first time I hear about that. If you mean that selection that happens at 17yo is based on grades and teachers evaluations since kindergarten - that might be, but it sounds different than "selection starts at 4yo" which implies that 4yo kids are selected and followed all their life.


> selection starts at 4yo" which implies that 4yo kids are selected and followed all their life.

I mean, they were followed all their life when they arrive at the final selection process, it is a track record after all


Yes, but they are followed then selected, not selected then followed. Which has totally different dystopian taste.


So when you said "Selection starts from age of 4", you mean that schoolchildren of this age receive standardised testing?

What does this have to do with the military? What does the "selection" actually entail?


What my daughters went through:

1) at age of 4 all the parents were gathered to meet kindergarten personnel. They explained that kids will play games all year. Parents were separated to groups and given logical puzzles to solve. Results were noted.

For the next two years children were playing games with changing rules to negate natural ability for specific game and to select for ability to find the best strategy within current constraints.

At the same time each parent is given a day to present his/her profession. Results are noted.

Results were passed to school class selection committee.

2) According to results in kindergarten kids are grouped in schools. Some are given opportunity to participate in electrical engineering or robotic activities (my daughter was Top 5 in Israeli competition for 6-9 years old with reduced team).

3) By the end of the second year some of the parents are notified that there will be an examination. Test is analogous to IQ (math, language, general knowledge). Graded on the curve for municipality. Top 8% are invited for one day a week for additional activities. Top 2% are invited to special schools with much more intensive program. My daughter made it to top 8%. Activities are: decision making, finding solutions within constraints, leading groups of people to solve bigger problems.

4) By the end of elementary, depending on previous results, kids get access to full math program (as opposed to reduced arithmetic). Additional activities include software and electrical engineering, robotics, chemistry, physics and so on. Parents and kids, that didn't made it to Top 8% at previous years, are not aware of these activities (invitations are sent personally).

5) At age of 15 kids pass initial evaluation by IDF. Good grades at high school will guarantee initial evaluation will be upheld. Bad grades will negatively impact the chances.

6) By the end of high school whole history and psychological profile are passed to IDF for final evaluation.

> What does this have to do with the military?

In Israel everything has everything to do with military.


You witnessed the hiring process of the NSO Group, which begins at 4 years old in kindergarten? For a company which has existed for 11 years?

I can't agree more with what the above commenter said. This is not infosec hiring, it's Spy Kids.


He didn't say it was NSO, but the Israeli military and specifically 8200


One person's boring is another's career culmination. Breaking system security often consists of dead end after dead end, and even if you get a lucky break, you may hit another dead end after that. Finding an exploit often isn't enough these days, they need to be chained together to actually get somewhere interesting. Personally, it's very unrewarding (aka boring, imho) work most of the time because you don't find anything a lot of the time. (The high off of finding something is something else tho, lemme tell you.) If you're interested in the sort of work involved, http://microcorruption.com is a good CTF to start out on.


Just a heads up to anyone using jq - I've previously spent a couple of hours debugging a problem because jq uses float64 to store integers (which might lead to rounding-errors/overflows). For example:

  echo 1152921504606846976 | jq                                                            
  1152921504606847000


This is an artifact of JavaScript, which even as of ES6 uses IEEE 754 double-precision floats for all numeric values. jq likely uses the same implementation internally for compatibility reasons and to avoid surprises of a different kind.

See https://www.ecma-international.org/ecma-262/6.0/#sec-ecmascr...


BigInt in top browsers now, not under a flag. Just sayin'!

https://brendaneich.com/wp-content/uploads/2017/12/dotJS-201... et seq.


I think an 'error out if overflow/truncation'-mode available as a command line flag could be useful if you just don't have any JS involved in the JSON pipeline.



Twitter had to switch their tweet id representation in the API to handle this - it was numeric and switched to strings.


Note: the links currently redirect to https://imgur.com/32R3qLv (image of a testicle and derogatory comment on HN)


Copy-pasting the link bypass this. It's using the HN referrer (I think?) to redirect to imgur


Yikes, that's nasty.


It is. But it's a problem of JSON itself, not just jq.


TIL: JSON has no specified number implementation: http://www.ecma-international.org/publications/files/ECMA-ST...

>JSON is agnostic about the semantics of numbers ... JSON instead offers only the representation of numbers that humans use: a sequence of digits.

So... anything is valid, per the spec.


JSON != JavaScript

> echo 1152921504606846976 | python -c 'import sys, json; print(json.load(sys.stdin))'

1152921504606846976


Python's json package != JSON

JSON: https://tools.ietf.org/html/rfc8259#page-8


The link says that it's up to the implementation, which means it's valid for Python's JSON implementation to support larger numbers.

It's less "interoperable" but not strictly invalid, by my read.


What the GP means is that JSON doesn't require an implementation to decode JSON integers as arbitrary-precision integers, to be "conformant JSON."

Therefore, you can't assume that if you pass some JSON through an arbitrary pipeline of JSON-manipulating tools, written in various languages, that your integer values will be passed through losslessly.

Therefore, you just shouldn't use JSON integer values when you know that the values can potentially be large. This is why e.g. Ethereum's JSON-RPC API uses hex-escaped strings (e.g. "0x0") for representing its "quantity" type.


It looks like JSON doesn't specifically define how numeric numbers should be stored. It just recommends expecting precision up to the double precision limits.

Still interesting to know it's not just a jq quirk.


Just because python has bigints and its stdlib json module supports bigints in json doesn't mean that is an interoperable thing to do.


The problem is made worse on the receiving end (the browser). I've ran into this issue when serialization libraries in Java send a 64-bit long value as a sequence of digits, then things over ~50 bits get silently truncated, you find out about it, then switch to quoted strings.


That's Python not adhering to the JSON standard as defined in the RFC.


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

Search: