HNHacker News
TopNewBestAskShowJobs

genezeta

1,671 karma · joined September 1, 2010

Just a random person who failed.
submissionscomments
genezeta··on “Cell Tower” Word Game
To add to the other answer...

The final goal is indeed to use all letters. If you just go around choosing words, let's say, at random, you'll end up with places where you cannot use some letters. Then you will have to unmark some "wrong" (valid but not the ones in the searched solution) words and try to find some other combinations that don't leave unused cells.

Note that a "score" is calculated when you reach the 100% filled solution. This score penalizes marking "wrong" words and going back and unmarking them. So if you want to not only solve the puzzle but get a good score, you need to be careful not to go too fast adding just whatever word you find. Instead, try to build words which don't leave isolated letters, e.g. start in a corner and build from there, or from the bottom, etc.

genezeta··on Ask HN: What's the coolest website you know?
Apparently, there's https://skinflint.co.uk/?cat=nb for UK, which could be more approachable for non-German-speakers :)
genezeta··on You need to know what right-half-plane zeros are
While I don't claim to have the answer to your question, I think there's a jump you're making that may not be so straightforward and somewhat explain things.

You say "people on HN seems to enjoy this kind of articles" which seems reasonable, given the comments here. But then you jump to "we think knowing theory is useful in cracking hard problems".

Going from the first to the second is not quite so clear. That is, someone may enjoy such an article and even learning some theory, but not necessarily because they think they will directly apply it. People sometimes just enjoy learning stuff or reading about it and then forgetting it.

You also make a second jump, because other factors may be involved. Maybe the theory asked in the interviews is completely unrelated to the things involved in the job. The job may not even require cracking hard problems. These are frequent occurrences -in my experience, at least-, and clearly seem compatible with thinking that knowing theory is good in general.

genezeta··on What if Oil and Gas Assets were priced for 2℃?
It's probably a better idea to link to the article itself rather than to one specific figure: https://www.nature.com/articles/s41558-022-01356-y
genezeta··on First Look At The CSS object-view-box Property
It hasn't been a problem for the backend or devop teams either.

The network load is... probably not something you, or me, can so offhandedly talk about here without the actual data. It depends a lot on which images are most used. I do know that they did in fact reduce a lot of bandwidth by serving pre-sized thumbnails instead of larger images. Typically there's only a few -3, 4- different sizes that matter; these can be -and are- cached by the browser. In this case, most visitors seemed to never need the full-size format, so that's a lot of saved bandwidth.

genezeta··on First Look At The CSS object-view-box Property
I know of at least one similar site where all that is achieved dynamically in the server. Images can be rotated, cropped, and resized dynamically. Common cuts can be made, cuts are cached, and making a new cut is done on the fly without noticeable delay by passing different parameter values.

This has been working now for about 6 years. It has never been a problem for the frontend team in any way.

genezeta··on YC W22 Stablegains is being sued for losing $42M in funds from 4878 customers
> the thing we call web3

The thing some call web3.

genezeta··on Many software companies are a joke
I don't really care much about what role was responsible. I commented it more for the usefulness of discussions/meetings.
genezeta··on Many software companies are a joke
One place I worked at some years ago...

We had this "important project" coming up, a certain big feature that was wanted in the platform. A project which would take about 6-9 months with the collaboration of various teams across the company.

I was involved but only in a helping role. One member of my team was involved but they were fairly inexperienced and so I was asked to go in as support.

After the first two meetings a number of things became clear. Mainly that the product owner for the project was extremely ambitious, clearly not knowledgeable about the technology involved and got very upset about any concerns or problems anyone would point out. They wanted "those stupid meetings" to be just for informing them of solutions and progress, not for discussing problems and options.

At the third meeting I made the mistake of mentioning that a particular detail, not too important, would be extremely costly to do as asked and that we would be better off doing it in a much simpler form. Unbeknown to me, that day the product owner went behind my back and asked for me to be immediately removed from the project. So I was. I didn't care much for it and I only learnt about that move much later, when I had already left the company.

Anyway, the project ended up taking about 2 to 2 and 1/2 years and it had to really reduce its scope in the end. And some of the people involved confessed that it was because of the product owner, because they had wanted people to "just build this thing I say and stop arguing". A lot of work was simply thrown away several times simply because of not having had the proper discussions it needed.

genezeta··on Using TODO For Everything
Hmm, in Spanish "todo" literally means "everything"...
genezeta··on We need someone who has done “it” before
Another common situation I've encountered is this one: They don't really want "it".

They say they want someone to do "it", they hire someone who has done "it". But then that wasn't really what they wanted done.

I think I can also draw the hypothesis that the more convinced they say they want "it" and/or the bigger the "it" they ask for, the less they actually want it when the time comes.

genezeta··on Four Eras of JavaScript Frameworks
> According to Wikipedia, XHR was introduced in 1999, 4 years after JS was introduced

Your way of commenting on XHR in this paragraph...

    In this environment, it’s understandable that JS was generally seen as a toy language and not something you’d write a full app in. The most common thing you would do was include jQuery, throw together some scripts for a few UI widgets, and call it a day. As time went on and XHR was introduced and popularized, people started to put parts of their UI flow into a single page, especially for complex flows that required multiple back and forth interactions between the client and the server, but the majority of the app stayed firmly on the server.
...where you are talking about jQuery already being a common thing, which implies at the very least 2006 but more likely 2008-9, and then writing "As time went on and XHR was introduced and popularized", suggests the idea that XHR somehow was introduced much later, when jQuery was already common.

This is what I was referring to. It may have not been intentional, but the way you comment and present it suggests a mistaken timeline.

genezeta··on Four Eras of JavaScript Frameworks
> IIRC the only option at the time for running JS on the server was Rhino (based on Netscape/Mozilla), which for whatever reason never saw the broad adoption of Node.

There was SSJS on NES/iPlanet/whatever before that. I mean, it existed. It was not really useful and few people even noticed it existed at all, but it did exist.

genezeta··on Four Eras of JavaScript Frameworks
In Spanish there's a saying that goes "Cada uno habla de la feria según le va en ella". It means that everyone tells their story, that they say the fair went well or not depending on how it went for them.

Another comment talks about revisionism and, while I think it is a valid critique, I think it goes beyond that. The author's career starts in 2012 and that's all the reference they seem to use.

Sure, they admit they will "probably going to gloss over a lot" and that they "can’t write about what [they] didn’t experience". But then... is this fair? Or, a better question -since anyone can write whatever they want, of course-, will this be, then, just some person's story or will it actually be representative or a larger reality?

Sadly, it feels like lately a lot of people seem intent in blurring that distinction. They seem to say "I may only have a limited view, but I'm going to present this as if this was the complete reality". And this is what this article does, I'm afraid.

The fact that there's is absolutely no mention at all of Dojo is telling. It's also quite telling that dismissing claim of "throw together some scripts for a few UI widgets, and call it a day", the quite absurd "everything was global", and the error of suggesting XHR came later -"As time went on and XHR was introduced and popularized"-.

genezeta··on Ask HN: Hybrid/Remote software team rituals
Blood sacrifices and invocations to see who can summon the cutest and fiercest beast. You show your demon to the camera and get votes on it and on the chants you did to bring it from the depths. At the end of each sprint.

Remote orgies to appease the gods of nature and ensure a good deployment. Everyone wears traditional handmade masks for anonymity and we only do it if all tests are green, obviously. Every three months or so; depends a bit on the moon.

Previously we tried more traditional stuff like fire walking but we had to stop doing that one because a guy in another team wasn't careful setting up the coal, ended up burning the company laptop, and then HR banned it ¯\_(ツ)_/¯

----

Edit (for constructive commenting):

I guess I don't like rituals. I much rather prefer a less forced environment for more spontaneous and relaxed communication.

That's not to say you can't have some habits or whatever, but I feel most of those "cool ideas" always end up feeling tiresome to some part of the group if they don't grow from the people themselves.

genezeta··on How Disney Became a Nuclear Power
Other things aside, the expression "a nuclear power" generally means an organization -usually a state- with nuclear weapons.

As such, if you search for nuclear power in general you'll find there are about 30+ countries in the world with plants. If instead you search for "nuclear powers" you'll find it refers to just 8 countries with nuclear weapons.

I mean, I know this is just stupid clickbait to make you think of something like the Pepsi Navy and grab your imagination. But it is still stupid clickbait.

genezeta··on Show HN: Find companies with jobs using technologies you love
> Is it a developer issue or the industry is being fucked up by hiring managers or recruiters ignoring portable developers Knowledge and just caring for how many years you’ve used $nextCoolFramework?

I don't really know whose fault it is, but I can tell you from experience that if you present yourself as having good -even excellent- experience and knowledge of the principles, the practices, and the patterns, and having similar experience with $similarFrameworkA and $similarFrameworkB, but not with $thisParticularFramework, then "you're not quite what we're looking for". And the opposite is common too. If you do have a couple of years experience with $thisParticularFramework you're good to go. It doesn't matter whether you don't know how to do anything else outside of that.

This is something people don't often want to admit, or sometimes even discuss. I'd guess it may be related in some way to another rarely admitted fact about the industry: There is a lot of wasted effort and resources. Particularly in certain types of projects and companies, the overall productivity is extremely low.

genezeta··on Ask HN: Developers who switched careers, what are you doing now?
I just left, after some decades, not switched to anything else.

Friend of mine though, he became a postman, about ten years ago. He was never quite happy being a software engineer. I see him occasionally and he's always happy with a job where he gets to work by walking around in the open most of the day.

genezeta··on Placeholder for a Conversation
> I don't care if the body of the ticket is empty and as the Engineer you prefer to write it in a notebook.

> I don't care where the conversation gets recorded, or at all (provided the people are capable of remembering it).

That -"provided the people are capable of remembering it"- is quite a restriction you got there. If some engineer writes it in their own notebook, some other one simply goes by their own memories, etc, then I'm willing to bet there will be different memories of how it went and at least some of those will be fragmented or lost. And every time you need that information, you'll find yourself having to re-search it, re-compile it, and reconcile it again. And then someone leaves and that perspective of the conversation history is lost forever.

I mean, sure, don't put the tool over the actual conversation. But then again, please, do use a tool to register history, key arguments, accepted limitations, relevant decisions, actions taken.

> This is strong evidence of a team working with extremely shared context.

Not really, no. It may be a reflection of that... or it may be a reflection of something else entirely. Like some people making small notes so they will remember and nobody else reacting to them. Ideas that come up but are never discussed afterwards.

The visible result of this can be exactly the same as what you describe and yet the situation is totally different.

genezeta··on When or If
Yeah, personally that's the option I would choose too. It should fall on Sass to change whatever they may need to.

It's not completely "kind-of simple" though, as there is, potentially, a fair amount of code written with Sass in currently running projects. It is a cost to consider.

Also, there have been some precedents in the JavaScript community, mainly with Mootools -an old library, mostly irrelevant today but with some existing code still running in the wild- and the name of a couple of methods such as includes and flatten. The thing is that TC39 really pushes for "not breaking anything at all", and by proximity the CSS community seems to have some people with a similar opinion.

genezeta··on When or If
There are indeed significant differences.

The main one is that Sass is, basically, a "code generator". It's a sort of template language that generates CSS code. And so, a "Sass-if" works at code generation time, that is, when you execute the Sass command:

    sass-if (some logical condition) {
        <some CSS code>
    } else {
        <some other CSS code>
    }
Depending on the condition and at compile time, sass would spit out the first block of code or the second. The condition is, basically, a calculated expression that applies to values and variables available at compile time.

Then -after deployment and when a client visits your website- that CSS code is served to the client. Clients are varied and so CSS wants to have its own if structure that applies at runtime. The conditions generally would check the current runtime conditions (i.e. is this running on a large screen? is this browser in vertical orientation? etc)

    css-if (some condition pertaining this specific current browser) {
        <some CSS code>
    } else {
        <some other CSS code>
    }
So, yes, they are clearly and necessarily different, both in scope and usage. And so you'd generally need both if because they do different things. And that where the problem arises, because if you want to have both, their syntaxes need to be distinguishable.
genezeta··on Stack Overflow Is Down
FWIW I don't see it being down from here (Europe). And I see "question asked 1 min ago" so it's probably working at least partially.
genezeta··on Ask HN: As non-nuke power, why fight a nuke power, esp if you have an easy out?
> Maybe you can just give the bully your lunchtime scooby-doo snack and live to fight another day?

Maybe you can just give the bully your lunchtime scooby-doo snack and go hungry, and again tomorrow when the bully demands your fruit and your money, and the day after tomorrow when he just punches you in the face for fun...? It's easy!

And why is Michael getting in the middle of this?! The bully is strong, isn't it better to continue being friendly to the bully while he expands his bullying to other kids in your class as long as they are not your closest friends?

Why doesn't everybody just either kneel before the bully or let him do his thing to others? I mean, the bully is just acting logically, trying to establish himself.

genezeta··on $1 Microcontrollers (2017)
> It would be great if someone could find it and put it in the title.

There's no publication date -nor anything marking it as updated at any time afterwards- on the article itself, but first comments are from November 2017 and passing references in the article point to "end of 2017" too.

genezeta··on Ask HN: How should one go about learning JavaScript?
It depends a lot on what your starting point is. That is, the approach will be different for someone who maybe isn't a programmer at all ATM, or for someone who has some experience with some other language, or has fairly extensive experience with other languages but none or little with JS. Or any other circumstances.

For someone with no programming experience at all, there are various opinions on what your first language should be, but in any case there's abundant material and courses that teach general programming using JavaScript.

For someone with programming experience but not JavaScript. Perhaps some of the stuff [1] written by Axel Rauschmayer may be good. Or maybe some other resources like "The Modern JavaScript Tutorial" [2] or this other one [3]. I used to recommend Eloquent JavaScript [4] also. I do think it is a good book, but feedback from various people indicates that is clearly not for everyone, so YMMV.

MDN (Mozilla Developer Network) is something you should keep at hand, but more as a reference than as a guide. It does have some learning guides [5], but in general I wouldn't recommend them that much. Still, do keep a link to the MDN as it is a very good reference to go look for specific explanations (sometimes).

All of those mentioned above will generally help you learn the language, which is what you should probably do first. My recommendation would be to have a first look at the links and choose something that matches your learning style. Still keep the others, since sometimes a combination of different explanations will make things easier to understand.

I haven't mentioned any libraries or frameworks. I know there are some courses out there which very quickly throw you into focusing on some framework or other. Personally, I would recommend against that, if your intention is to learn JavaScript well. At least initially.

There are also some "JavaScript Roadmaps" out there. I mean stuff that looks like this one [6] -but not that one, which is for frontend development in general-, a huge chart/list/map of concepts and ideas that are supposed to cover "everything you need to know". I would not recommend following those. While they look impressive and pretty, they can also feel overwhelming while not providing any particularly good path to follow.

[1] https://exploringjs.com/

[2] https://javascript.info/

[3] https://learnjavascript.online/

[4] https://eloquentjavascript.net/

[5] https://developer.mozilla.org/en-US/docs/Learn/JavaScript/Fi...

[6] https://roadmap.sh/frontend

genezeta··on Fengari – Lua for the Browser
Don't take my word for it as I only looked into this a while ago but, if I remember correctly, you'll probably need to:

a. First build a function in JS wrapping the usage of fetch and the management of the JS Promise there. You'd use lua_yield and lua_resume to yield, and to return back to lua the appropriate value. You would, optimally, do this just once. Or maybe someone has already written such a wrapper so you would simply require it; you'd have to search around for that.

b. Once you have that, in the Lua side, you would simply wrap your calling code in a coroutine and you don't need to use any await or then or anything. Something like...

    coroutine.create(function()
      local r = fetchWhatever(url, ...); -- the wrapper mentioned above; you just call it
      print(r)
    end)
But again, don't take my word for it. Things may have changed since I last looked at Fengari.
genezeta··on Fengari – Lua for the Browser
According to the description, a minimal glance at the code and this [0], no, that's not it.

It is "the Lua VM written in JavaScript" and "largely a port of the PUC-Rio C implementation of Lua". It runs the Lua code on that VM, so there's no transpilation.

[0] https://hackernoon.com/why-we-rewrote-lua-in-js-a66529a8278d

genezeta··on Fengari – Lua for the Browser
Once you local js = require "js" you have direct access to the JS global object, so you can...

    js.global.fetch(...)
genezeta··on Mozilla Foundation places two-page advocacy ad in The New York Times (2004)
> If it's not broken why do so many devs refuse to support it because things they code in Chrome don't work in it.

You'll surely meet a lot of people doing what you mention. I would bet most of them are young enough to not have gone through the so-called "browser wars" [1], at least what they now call the first one, the one that ultimately led to the creation of Firefox.

Their attitude does not mean at all that there's something actually broken in Firefox, just that it is so much easier -and lazier- supporting a single browser's quirks and ignoring the rest. Even if that means discarding standards and compatibility. Specially if it means that, because you will take advantage of those particularities.

[1] https://en.wikipedia.org/wiki/Browser_wars

genezeta··on A simple system I’m using to stay in touch with hundreds of people
Oh, hi :)

I hope I didn't say anything inconvenient. I sincerely appreciate you even if we've never met.

And thank you for the clarification, of course.

← PreviousPage 14 of 19Next →