HNHacker News
TopNewBestAskShowJobs

genezeta

1,671 karma · joined September 1, 2010

Just a random person who failed.
submissionscomments
genezeta··on A simple system I’m using to stay in touch with hundreds of people
Derek Sivers seems kinda cool. I mean, I used to read him back in the times of CDBaby and he seemed like a nice person. Of course, I can only say he seems so because I haven't really met him. I don't know him.

Later, I would receive some of his emails and while they always did feel honest and thoughtful, I always understood we'd never even talked to each other. Sometimes I could think it was "just a commercial email" to present this book or whatever. Other times he would just sort of talk, about things in his life, "without anything to sell". But whatever the case it was clear I was "on a list".

----

I keep very few contacts. Probably too few. There's only a handful of people I talk to regularly. There is a woman I love quite dearly and we talk on the phone maybe once a week, sometimes less, sometimes more. Some other very close friends, less than I can count on my fingers, and again we talk occasionally, randomly. Maybe every few days, maybe once a month or less.

I have been postponing visiting them because of other personal circumstances, but we know that's just how things are at the moment and that we'll see each other "soon". Those friendships will not disappear even if, for whatever reason, we don't get a chance to talk or see each other for a couple of months or longer.

There's also a larger number of acquaintances. Friends, but less close. Ex-coworkers or ex-colleagues. There's this group that likes, say, comic books and I'm giving away my collection. So I might just throw an email in their direction because I remember they liked that. Someone may be interested. We'll meet and talk about whatever past and present we may have in common -or not-, maybe have a drink or a tea or maybe not, I'll give them the comics and then maybe I won't see them again for years. Maybe forever, because life is that way and you never know.

----

I've always felt Derek's approach to keeping in contact... interesting. I mean, if that works for him, then great. But I think that the system is a lot more for his benefit than for the benefit of the relationships themselves. And again, great for him. I mean it. But I don't feel the need for such a system for myself and I feel like not many people do.

genezeta··on Show HN: A daily math puzzle inspired by Wordle

    Uncaught SyntaxError: Octal literals are not allowed in strict mode.
genezeta··on Show HN: A daily math puzzle inspired by Wordle
If you write a number like 05 there will be a...

    Uncaught SyntaxError: Octal literals are not allowed in strict mode.
genezeta··on Annoying React useState mistake I've seen senior engineers make
I want to be helpful. Please read the following with that in mind.

----

I don't want to throw the question of "Does this really need to be a video?", because, well, you seem to have built this idea of "coding shorts" and it wouldn't make much sense to call it that if they weren't videos. I also don't want to challenge the duration because, again, well, they are "shorts". But then again, I'll ask "Is this good/helpful as a short video?". Or if you prefer "Does this use the medium correctly to actually be good/helpful?"

And my impression, I'm sad to say, is that the answer is a very clear no.

I won't even discuss the fact that this is not a mistake I've seen senior engineers make. You may have. But how often? Anyway... There are some problems with your presentation.

The main problem is that you don't explain anything. You don't explain the problem, nor the cause of it, nor the solution.

In fact, there's a point, starting at around 0:15, where you remain silent and just move the mouse around, clicking, expecting the viewer to... I don't really know what you expect of them. I mean, if the viewer is supposed to be familiar with that sort of code, you don't need that at all. You would just say "...increases the counter every time the button is clicked" and simply continue. If you don't expect them to be familiar with that, then they will gain nothing from moving the mouse around silently clicking here and there.

Then you demo the thing a bit. "If I change this to two, the counter increases by two". And, suddenly, again without any explanation at all, you duplicate the setCounter line. Why would you do that? We don't know. You just do. And so, when the problem you wanted to show appears, we don't know why it would appear in real life. I mean, why would someone duplicate that line to increase by four instead of just doing the exact thing you did a couple of seconds ago and change the 2 to a 4?

And then you even claim "it still increases by two and not by four as you'd expect". But why would the viewer expect that at all? In fact, I'd argue most people -or at least a large percentage- would see the duplicated call and just think "duh, why setCounter to the same value again?". So, again, you are assuming some expectation from the viewer without explaining in any way why would they expect that.

Ah! "The reason for this...", now we're getting some explanation. "...is the way that React works." Oh... "React bundles rendering state together; each setCounter does not correlate to a DOM update". Well, but that doesn't seem to be the problem at all. The problem is not that the UI is updated out of sync or something like that. If the problem was about the value and the DOM being out of sync, then at some point the updated value would be reflected somehow. So the explanation leaves the viewer with a confused impression. It is also given offhandedly as if of course they were supposed to know that, which kind of makes the video pointless.

The actual problem is that the value is being updated twice, but with the same value both times. That when you call setCounter, counter itself does not get immediately/reactively/magically updated, and so if counter is, say, 8, you're calling setCounter(8+2) and again setCounter(8+2) a second time.

Finally, you offer a solution: "do something like this". Again, no explanation. Not only no explanation of what -well, you just write the code, so let's assume the viewer clearly sees what the change it- but more importantly no explanation at all of why. No explanation of why using a function changes things, of why it now works.

All in all, I'm sorry to say this but it feels like the poster image for the video -you know, the one with the bad code on the left and good code on the right- gives just as much information -or as little, really- as the whole video itself.

----

So, again, trying to be constructive...

I'd say you need to improve a number of things.

First of all, start by defining your intended audience, what they should already know and what not.

Second, don't just make up a problem, present and explain an existing one. That means that you don't just duplicate that line with no explanation, instead you do the complete opposite: you explain why and how someone would be walking into the problem.

Then once you've shown the problem, first give an accurate explanation of why the problem occurs. Here the key is the first point, knowing your audience. If someone were to walk into such a problem, they won't know that obvious reason, they won't know what you mean by "it's just because it works this way; state rendering is bundled, obviously".

And finally, once you've explained the problem and go onto giving a solution, again, explain that solution, what it changes and why the change is actually significant in the context of the problem.

genezeta··on Deskreen: Turn any device into a secondary screen for your computer
> We're really sorry, but...

> Mozilla Firefox Browser is currently not supported, due performance limitations.

:(

genezeta··on Adding unusable RAM for tax reasons
> The CPC472 itself was sold for how many? pesetas (how many? euros)

As far as I can remember, the CPC472 was sold for the same price as the CPC464. It was never marketed as an actual improvement over the 464 and competition in the market was hard enough to be able to justify a higher price without a clear justification.

Then again my memory is not that good now so anyone feel free to correct me.

genezeta··on I think I know why you can't hire engineers right now
It's kind of funny -but more like funny-weird, not funny-haha- when I read some of these articles.

I don't mean that in a bad way. The article is well written and, to some extent, well thought. The problem is they usually -as in this case- extrapolate a fairly limited experience to a very general explanation of just about everything. This can be also noticed in some of the absolutely tiring clichés of engineers being Trekkies and dorks and whatever. But more than that, it usually ends up being that the conclusions reached are mostly a mishmash of reasonable things which miss the point, at least as a general explanation.

But, as I can't consider myself an expert in the USA job market -or should I say "the quite specific USA FPGA / RTL design engineers job market"-, I'll do something else instead. I'll paint you the picture of a very different market, the Spanish IT job market. The common point is they also whine a lot about an engineer shortage and a lack of available skilled force.

Here the market is defined by the following:

- The market is mostly dominated by a handful of big players. At the tipping point, there's maybe 6-8 large companies that hire a lot of developers -even though I personally think they don't really need so many-. These are, mostly, bank and insurance. There's also one or two more directly IT related.

- The market is actually layered through a pile of leeching^H^H^H^H^H^H^Hconsulting companies. There's an initial layer of larger "IT consulting" and "IT Integrators" who provide the above banks and large companies. Then there's the smaller ones which mostly provide bodies to the bigger ones. It is not uncommon for a particular job to involve at least 2 subcontracting steps. It's also not uncommon for them to lie about it at the beginning of the hiring process.

- Salaries are being contained or even lowered right now. It's hard to break around this because of hidden price collusion. Right now, as I said, salaries are low. Every time someone mentions "talent shortage" there's at least half a dozen of comments saying "well, pay more" or "don't pay so low, then". Personally, I'd say that most IT related jobs, and particularly those that actually create/operate/maintain the things, are being pushed into being considered as an "operator level" job. Low pay, easily disposable. Experience is, generally, an uninteresting trait beyond 2-3 years, and job offers reflect that. Entry level jobs are, again, paying low to very low. I know it can't be but it all feels kind of orchestrated. I mean, it can; it has been done before, but I'd rather think it can't be.

- Job offers hardly even mention anything. I've seen some hiring companies which will simply not put any details at all, not even technologies involved or anything. In any case, there must be fierce competition there because they all tend to be more secretive than usual. Not only will they not give you the name of the company -which may be understandable- it can sometimes be hard to even get general information like what sector it works on or an approximate location. This is most frequent, obviously, when it is not one of those big, few banks or insurance companies.

- Hiring processes are mostly clueless. They are heavily focused into that "operator mode" and usually ask for stupid things like very specific versions of tools -e.g. like "I see Spring Boot mentioned in your resume, but which version? You don't mention which and I'm looking for version 2.5.x" or "I need to ask you exactly how much experience in years you have with Angular 8 and how much with Angular 11"-. You can easily have to go through technical tests -and I mean things like building a 40+ hour demo project- even before they will even talk to you at all. In a couple of cases these were so specific and large one could even wonder if they were actually getting some smaller tools done for free through this.

- Job security is mostly a myth. During 2020 and 2021, quite a few of the big hiring companies and many of the body providers simply dropped hundreds or thousands of developers with little more than a snap of their fingers. To some extent they are trying to re-hire now, but not as much and, naturally, with lower salaries.

- There is, sure, a smaller market where smaller companies hire. This is a bit of a hit or miss. Most of them don't/can't pay too much but are, usually, better places to work at. There are also a number of startups -and companies calling themselves "a startup" because it's cool-. Most of these come and go, of course, and only a few of them aren't working on yet another "customer experience optimization" thing -i.e. tracking and advertising- or on "online gaming which actually turns out to be online gambling". One or two of those startups have even thought about a business model that is not crossing their fingers very hard.

- There's also the "agile market". Even if you like Agile, this is a circus. I've seen ratios of "agile coaches to sw engineers" which would make anyone wonder if anything is done at all in there. And the answer is no, obviously. I spent some months watching one of those big banks which don't want to be called a bank any more and it was absolutely ridiculous. I vividly remember some sort of retrospective meeting or whatever they called it where literally everyone was lying to avoid saying no progress at all had been made in the last 3 month period. And everyone knew everyone was lying. And still, these "agile coaches" were doing some happy dances and saying "good, good, this is very good, we're doing very well". I don't mean this as an attack on Agile, but more on the fact that it has been co-opted to burn loads of money at some of these larger companies. I mean, it's business as usual, but now under the name of Agile. It's sad.

All in all, here in Spain the answer to why it's hard to find engineers right now is... it isn't. But some players have twisted and broken the whole system so much that the job isn't that interesting any more.

genezeta··on Ask HN: How do you deal with the powerlessness feeling of coding?
> For the last few months I've been learning back Django which was my first love. I'm learning back the django rest framework and today I have an issue where in the DRF interface the button for POST/DELETE/PUT/PATCH don't work. They don't even send the POST/DELETE/PUT/PATCH request, they just reload the page as if the only thing those button do where `window.location.reload();`.

It's hard to know for sure without actually seeing it, but...

This sounds very much like a fairly typical JavaScript problem. Or to be more precise, a "lack of JavaScript" problem. Let me first explain what I think may be the problem and then how you could look into solving it.

The problem as described makes me think:

- There is a button which submits a form. It should use an XHR for the submission, which means there should be some JS event handler attached to the button.

- But instead of that, if for whatever reason the handler was not attached correctly, then the button would simply submit the form it belongs to in a default way, which would reload the page. This fits the description you give.

So, first thing, how can someone go about verifying if this is indeed the case of what is happening?

What you do is you open your browser development tools and look around for a couple of things. First, you load the page normally, and do not yet click the button. Now, you look in the console for any JS errors at all and, if there are any, see if one of them maybe either a. related in any way to the button, the form, the event handlers, etc, or b. there is one that breaks JS execution, which would prevent other code from being run. More: You inspect the button itself with the DOM inspector and verify if it actually has any click event handlers attached. Note that it may be the case that the handler is attached as a submit handler on the form, instead of as a click handler on the button. If there is neither of those, then it's very likely that something has prevented some piece of JS from being run and the handlers from being attached.

After looking at that, still with your browser dev tools open, you set the network tab as visible, and then actually click the button and trace what happens. There's a lot to learn about browser dev tools, and there is a lot of info out there, so when you have a chance, that's something you could spend some time on. But right now you just want to check the request that happens when you click the button. In particular you need to look at the type of request and the "initiator". These will tell you whether it is indeed a "normal form submission" or an "XHR request".

Once you verify these things, if this is not the problem, then you'll need to explore other options -which I cannot specify more due to the lack of information, of course-.

But if this is indeed the problem, that there's no event handler attached and the form is simply submitted, then you need to investigate why there is no handler attached, obviously.

Again, try to search for any errors in the console, check id's used on the form or button, check the template that generates the button and form. Also check the network template for any 4xx, 5xx, or any files that are not loading for whatever reason. It may be a misconfigured path, a missing library, a misconfigured MIME type... It can be a lot of things.

If you can't find anything like this that gives you a clue, then it's time to change the approach. Now start by looking for the origin of that button in the source. Where is it created? How is it created? Does it depend on any parameters? Are those correct? Does it depend on a global configuration? Is that correctly set up?

I can't tell you anything more specific than this, but that is how you "go about solving the problem". At some point, you'll most likely find a misconfigured path, or a missing file or parameter. Or, at the very least, you'll find an error message that can give you a clue of what is happening and what should be your next step. With that it will be much easier to ask questions.

----

So, in summary, you fight the powerlessness by actually trying to figure it out. There is no secret, really. There's no magic thing people do to solve problems we haven't seen before.

Note, also, that I cheated a bit. That is, going from your description I offered an experience I have previously had. But what if it was my first time? What if I had never seen this? The idea, then, is to first establish what is actually happening. You suggest "...as if the only thing those button do where `window.location.reload();`". This is an hypothesis. So you verify it. You do the thing with the browser dev tools -which you learn to use beforehand, of course-, and try to verify if your hypothesis is correct.

There's a small catch, though. Your hypothesis there is a bit "too sophisticated". Why would someone attach some JS to do location.reload()? Could there be an easier explanation? That's where the above comes into place: if you attache no handler at all, the submission is just a normal form submission; if the form has no explicit action declared, it will POST/GET to the same current URL.

So, in a way, that is a small secret -but really, it's not secret- thing: always start verifying from the simplest things. Always check the most simple hypothesis. This can even be extensible to "always check the most visible/obvious things", like always checking the error console and always giving the network tab in the dev tools a look for 4xxs or 5xxs.

Also, as already mentioned: owning the code. But this does not necessarily mean making the calls. Sure, you did not make the decision to use DRF, ok. But you can still make the effort to learn DRF to a desirable extent.

genezeta··on Ask HN: How do you cope with being interupted?
I think you got two different things mixed there.

One is being interrupted, the other is being distracted. Being interrupted is external, while being distracted is internal.

So which one is it you're having problems with?

Personally, I have come to accept that there will be interruptions. Colleagues asking for help, someone asking a question, some boss calling an unexpected meeting, my mother phoning or whatever. Some of these you can avoid; like you could have a rule to always communicate meetings in advance. But at least a part of these will be unavoidable. How many depends on particular circumstances; e.g. being a senior engineer in a mostly junior group means you were specifically hired to be interrupted to a considerable extent.

One thing that sometimes helps me with interruptions is using 5-10 seconds. That is, when someone comes I just ask for 10 seconds, I make a gesture or simply say "10 seconds" or whatever, and then proceed to sort of "unload". I write down the precise point I am at and the exact upcoming action I was going to take.

On the matter of distractions, it depends a lot more on yourself and the success of anything you try will be very dependent on how you are.

In this front, one thing I do is scheduling. I want/need to do X... but I have to do Y now. So, I slot it into an appropriate time. e.g. "This weekend I want to make progress on that personal project". So "this weekend". This means: a. not now, and b. I have sort of secured a time for it, I don't have to worry about it because it has an assigned place.

Again, in this area what works for others may not work for you. But also, as someone has already mentioned, if you can't manage to learn how to do this on your own, reaching out to a therapist or other professional help is a valid solution. They may provide more specific tools and techniques.

genezeta··on Ask HN: What is your spiritual practice?
XD

I'm still going nowhere, but at least I enjoy the views on the way.

genezeta··on Ask HN: What is your spiritual practice?
Not religious and not really spiritual at all to be honest.

The closest thing to "spiritual" that I do is walking slowly. Years ago one day I noticed I had the habit of walking very quickly everywhere I went and that this was pointless. I walk much more slowly now, looking around, watching things, people, anything. I make a point of always leaving earlier than I need so that I never have to hurry.

Kind of like the reverse to the chorus in "Nowhere fast".

genezeta··on “Zero fucks given” in other languages
In Spanish, I'd say "me importa un pepino" ("I care a cucumber") shares as much popularity as "me importa un pimiento" ("I care a pepper"). Personally I've heard/used the second one a lot more, but I guess it may depend on the region or something.

But there are other, more explicit, expressions equally popular. There is "me importa una mierda" ("I care a shit"), and the most vulgar one is probably "me suda la polla" ("it makes my dick sweat") or, for short, "me la suda".

genezeta··on Ask HN: How are your interviewers being rude to you?
This happened about Q1 2019 or something like that IIRC.

I went into the interview with a couple of red flags already. The main one is that the person at the recruiting company told me something like I should go in "with an open mind and calm", that they were very "harsh" and they used to do "very tough interviews" and that other interviewees had commented they didn't like it much.

Anyway, I went in.

I met with the Chief People Officer and the Head of Engineering, and yes, right from the start they were... I don't know, maybe they just had a somewhat impatient tone. Not too bad. But as we went on, they got increasingly so. They tended to cut me short on all the questions they asked. I know I sometimes do talk too much, so I just tried not to and that's it.

It was... a bit weird, but just that. It didn't feel that tough.

Then they asked about me having imparted some classes and trainings... "Maybe, 5, 6 people?"

    me> Sometimes more, like 10 or 20. It depends.
    them> Yeah, so then you feel a knot in your stomach, right?
    me> Ah... no, not rea...
    them> What are you, made of stone??
    me> Well, no, but I've done it many times so I don't rea...
They kept interrupting and trying to lead me to say whatever things they wanted. Since I wasn't, they got increasingly aggressive, sometimes raising their voice unexpectedly. They took turns at interrupting, at repeatedly asking some things, etc. They always asked things in the negative e.g. "you surely have never worked with..." or "you probably only know basic JavaScript, right?", and most of that was already in my resume so I had to answer by correcting them a lot.

After this went on for maybe 30-40 minutes, they finally got enough of it and offered if there was anything I wanted to ask.

They hadn't really told me much at all about their project, technology... really about anything, expect for a very generic overview. So I did want to ask. I started with something I thought easy.

    me> So, you mentioned this is a Java project; is it Spring based?
    them> That's none of your business.
    me> Sorry?
    them> You don't need to know. You'll be working on the front so whatever.
    me> Well, I would like to have a better overview of the project. Knowing the technologies may give me a better idea of the general state of the code...
    them> THE CODE IS FINE. We wrote it and it's great code.
    me> Yes, of course, sorry. I didn't mean it that as not being good, just get an idea of the age, the general structure...
Very reluctantly, they explained that it was a Struts (1.2.x) application. But not really. Apparently they had sort of forked Struts internally to do some "tricky stuff" from the JSPs, or whatever. They were really unwilling to explain much at all and the little I got out of them was with constant snorting and chuckling at anything I asked clarification for, like I was waiting their precious time.

I would have but didn't dare to ask much else. And I had lost all interest anyway. So we ended the interview after a few more minutes. I kindly said goodbye. The CPO was amiable enough to shake my hand -again, this was mid-2019- but the Head of Engineering didn't feel like doing that and simply remained seating looking at something or other on their phone.

This would have been weird enough. The next day I spoke to the person from the recruiting company. I told her, without going into details, that I felt they had been quite aggressive, even to the point of being rude. She laughed nervously and agreed that they could sometimes be "a bit abrupt". Anyway, I told her, I wasn't interested; I didn't think any good could come out of that. KTHXBAI and that's it, I thought.

But somehow, it seems they asked the recruiter for my number and, for whatever reason, she agreed and gave it to them. So about a couple of hours later, an unknown number calls and it's the Head of Engineering. They are... well, not cordial, but at least a tiny bit more agreeable than the day before. They ask what I think, about the project, the position, the offer...

    me> Ah, sorry. I already told [recruiter] from [recruiting company]. After our interview yesterday, I don't think this is what I am looking for. The project seems nice but at this moment I'm not interest...
    them> OH, YEAH?! Well, then just know that WE'RE NOT INTERESTED IN YOU EITHER!!
And click, they just hanged up on me.
genezeta··on Pico CSS Framework
Looks like they are still in use. At least, this is SCSS based [0] according to the docs.

Also, in another comment someone mentioned their own Sakura CSS and it's also SCSS based.

[0] https://picocss.com/docs/#customization

genezeta··on Pico CSS Framework
It appears to offer a reasonable opportunity of customization [0]. Of course, you may end up messing it and losing some of the consistency.

[0] https://picocss.com/docs/#customization

genezeta··on Show HN: A simple hand drawn HTML/CSS theme
Also in this vein: PaperCSS https://www.getpapercss.com/
genezeta··on Web3 Is Not Decentralization
> The whole Web 1.0, 2.0 and 3.0 has never been a good fit anyway and used quite arbitrarily

The actual problem is that there's a fundamental distinction between the "2.0" -and "1.0"- tag and the "3.0" tag.

"Web 2.0" was a term coined to describe something which had already occurred, at least to a substantial extent. This is made obvious by the fact that it was coined in conjunction with "Web 1.0". It was defined on some -more or less defined- characteristics that were there already and were used to point out a change that had already happened. It was "Ok, this has happened; let's call it 2.0 (and, for contrast, let's call 1.0 what existed previously)". People generally agreed on the name and that was it.

"Web 3.0" was never anything like that. It has always been co-opted to promote someone's ideas/hopes/vision/technologies. It is always "Ok, I/we want to go in that direction; I/we will call that "3.0" and hope the world shares my view and allows me to use that name for my vision". As a fairly old example:

> The Semantic Web (sometimes known as Web 3.0) ... [0]

But, of course, being something which isn't there just yet, a lot of groups want to own the term for their thing.

[0] https://en.wikipedia.org/wiki/Semantic_Web

genezeta··on Ask HN: Software Engineer hitting 40: what's next?
Similar age and circumstance but not in the USA.

The saddest part for me is the companies that just throw you a take-home exercise without even bothering to phone you first. You apply to a certain position and then, say a week later -or sometimes more-, they simply send you an email with some programming task to develop.

Frequently they are not small tasks but full projects which require multiple days of work. Just a few days ago: delivering a full web application to manage "map layers", with a DB, a back-end, and a "user-friendly front-end with a nice design"; testing included and all put into Docker containers, and a working demo somewhere published automatically from the repository.

And I mean, it's not just the assumption that you will spend however long it takes you on this for free, but that you will do it without even having had a simple conversation with them before.

----

Anyway, what I really wanted to say was: Good luck in your search. Stay sane.

genezeta··on Remix – A framework focused on web fundamentals and modern UX
> If you look at this example[0] you'll see there's not a single useState, useEffect, etc.

Sorry to point it out, but there is useRef, useEffect and a useUserData on lines 48, 53, and 47 respectively.

genezeta··on Show HN: Windows 2000 on Docker
I'd guess that the "don't expect any security" comment above meant exactly that. Not that you should forgo security, but that you should expect this to provide no security at all.

Some other comments mention browsing with IE5. You should expect that to provide no security either.

genezeta··on Facts every web dev should know before they burn out and turn to painting
Then again, sometimes it's even harder to take the "DRY nothing" out of them once they decide "DRY everything" was wrong but misunderstand why.

I mean, while the explanation above is nice, it's fairly easy for a junior to speed read through it as "DRY is a luxury [...] You should repeat yourself [...]" -ignoring all the parts that sound too complicated or nuanced- and quickly jump to the completely opposite conclusion.

genezeta··on We Tried Baseball and It Didn't Work (2006)
On the other side of the analogy, Mr. Jeffries & co seem to think that:

- Everybody should "play baseball"; playing baseball is the perfect way to "have fun" because "the proponents of baseball" said so.

- If you aren't having fun, then you're not playing baseball correctly; Playing baseball correctly necessarily leads to having fun.

- Softball is just plain wrong; lots of people play softball and seem to have a lot of fun doing it, but they are clearly wrong and not having fun because they don't follow the rules that the "proponents of baseball" dictated 20+ years ago.

- Oh, yes, I sell baseball courses; but this doesn't make me biased at all when criticizing other baseball coaches or even other ways of having fun. It's just that all the other ways are wrong, always.

genezeta··on Tricks I wish I knew when I learned TypeScript
The final version of sortNumbers is:

    function sortNumbers(array: Readonly<Array<number>>) {
      return [...array].sort((a, b) => a - b)
    }
And sort sorts in place and then returns the sorted array[0]. So here the newly created [...array] is sorted and then returned by sort and then by the return at the start of that line.

[0] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

genezeta··on Reddit uses “reddit.com” itself as the endpoint for logging usage data
> Actually, it makes me wonder what's keeping these companies that want to serve ads generate JS dynamically server side and include the code for ads in the same file as the main application logic.

First reason is the lack of trust. Or limited trust, if you prefer. That is, SomeCompany may trust AdProvider enough to include their ads in its website, but then again not trust them enough to bundle random external code with their own. Letting the user's browser load from different origins does give you some separation.

Then there's the separation of responsibilities. Say something does break -and not because of blocking-, having the code bundled together makes it very easy to start a game of passing the blame. "It works for us", "We're not doing anything weird", etc. And not only that. There's also the question of who pays for that downtime. SomeCompany is kept from earning money, will AdProvider compensate them? SomeCompany'll probably need to provide evidence that the problem comes from AdProvider.

On the other hand, some websites may already be doing a very similar thing... though it's likely just accidental. I mean, I have experienced a fair number of websites breaking when googleanalytics is blocked and I'd bet it's not intentional, just bad programming.

genezeta··on Explaining how the MASM 2-pass assembler works
> (is?)

Yes, it still is. It's no longer supplied separately and instead is included in Visual Studio (or in the "Build Tools for Visual Studio"), but it is still there. Newer, 64-bit, version is called ML64 but still referred to as MASM/Macro Assembler.

genezeta··on Send Email Directly from JavaScript
The claim in the title is not "use JS to trigger the sending of an email from a server" but "send email directly from JavaScript".
genezeta··on Send Email Directly from JavaScript
> not as a service that allows you to send email from Javascript, but rather as a service that allows you to create a predefined set of emails via the dashboard, and then just trigger the emails from the Javascript. This is quite similar to how emails are usually sent via a proprietary server code

So... a bold title saying something and then an explanation explicitly saying it was not true.

genezeta··on The art of not taking things personally
I don't know if this may help you or not, but...

Let's pick that example of the manager and arriving on time. You have built two scenarios. In the first one you are "less important", in the second they are "lazy". I can see a couple of problems here.

The most immediate one is that there exist other possible scenarios. These may go from one extreme to another. I mean, I could imagine your manager being "evil", doing it on purpose to assert their authority over you, to make you feel who is the boss. I could also imagine some other extreme where your manager is giving you leeway for you to be the one who calls the meeting; they give you time to prepare or to tell them when you're ready. These scenarios may or may not apply, of course -I do not know your situation-. But they are not impossible. And in the same way there may be other possible scenarios.

The second problem derives from the fact that you focused only on those two possible scenarios. What do those two have in common? Both are negative. They put the reason for what is happening either on your manager's character flaw or on your own lack of importance. One might guess that you arrived at these scenarios by "looking for a problem". Given that you were looking for something negative, you only arrived at negative scenarios.

----

What could be done?

You could avoid arriving only to negative scenarios by avoiding looking for "a problem". Looking for a problem easily ends up finding one in yourself. And then as a defence mechanism some other scenario will appear by trying to "shift the blame". In fact, your second scenario almost feels like you came up with it as a response to find a reason so that the problem is not with you but with the manager. In any case, if you start by looking for a problem you will end up finding problems.

Instead you may try two different approaches. In one you force yourself to consider that the originating reason for this situation is not -or at least may not be- a negative one. You force yourself to come up with scenarios where there is a good intention or a positive motive, even if the result is one that irritates you. You don't even have to believe these scenarios are real or correct, just allow that they might be possible at least as much as the negative ones.

The second approach goes one step beyond this. The idea is this one: So there are a number of possible scenarios, but you don't really know which one is the "correct" one. Ask yourself: Do you need to care? That is, does it really matter what is the real reason this happens? Sometimes you may need to care, sometimes not really. This depends on you, mostly. I mean, the delay on the meetings may be important to you but not to me. Or vice-versa.

One small piece of advice here: Sometimes you may think that you do care, that it is an important matter and that you want it solved/fixed, but if you give it some calm thought you will find that you actually don't care that much. So just spend some effort here identifying what is really important and what is not so much.

Either way, you may care enough to want it fixed -or at least to go further- or you may not really care that much. Now, I focused on you caring about it, but there's a second factor you should consider: Can you actually do anything about it? That is, given the various scenarios and possible reasons, can you act on any of those to change them or are they all external/out of reach to you?

Now you have four possible outcomes:

- You don't care that much, and you can't act on it. Then just accept it as it is and go on. You can't do anything about it but you have also learned that you really didn't care so much, so this is something which shouldn't bother you.

- You don't care that much, but you could fix it. Then it's mostly a question of "choosing your battles". you'd have to see how much effort would it take to fix it and balance it with the possible benefit. The benefit will be generally small, because it's not something you really care about. Either way, if it's worth it or not, the outcome should be satisfactory. In one "you don't gain much but it didn't cost you much either", in the other "you don't fix it because it cost too much, but you didn't care so much about it anyway".

- You do care and you can fix it. Then do fix it. It's all in you hands, right?

- You do care but you can't fix it. This one is the problematic one. In a more stoic approach you may choose to "let it be". Accept that you can't fix it anyway so "learn to live with it". Sometimes this is enough. Thing about the meeting situation. You won't be able to change it, all the reasons you find for it are out of your control, there's nothing you can do... but you can still choose not to let it bother you. You might choose to use those minutes for something useful, like mentally preparing yourself for the meeting, or checking the list of things you want to address so you don't forget any, etc. The situation hasn't changed but you have changed what you make of it. Of course, this doesn't always work for everyone, so another approach is this: make it so you can actually fix the situation. I mean, all the possible scenarios you've thought of are... well, in your mind. So, a first step would be to investigate the situation. You may e.g. watch your manager's behaviour with other people: is it only when meeting you that he is late or is it with every co-worker/non-customer? May be it happens with some but not all? What do those do differently? Or maybe your manager is actually expecting you to remind them of the meeting? Maybe you could try doing that once and seeing how it goes?

In any case, my advice would be a mixture of both approaches. Make an internal and honest effort to just accept that you cannot change some things and make the best of how things are. But still keep your attention on identifying things that you might actually be able to change.

The background effect this approach has is that you learn to look for many more possible scenarios other than just "either it's a flaw with myself or I can blame it on someone else". You learn to accept that sometimes it doesn't matter that much why something is the way it is, and that you can still make something out of it, and you also learn to give "positive reasons" a change as the origin of a situation.

----

Im not really sure this can help you much, but I hope it does at least a little.

genezeta··on Simulator of digging a tunnel through the earth
I did not choose to be pedantic and I'm sorry you concluded that. I also did not get much meaning into your own comment other that it suggested there was "more to be seen".

I commented because, having tried it on desktop and then on mobile, the experience is still fairly similar. Most people commenting on it "not doing much" were generally expecting more functionality -e.g. some additional visualization of the tunnel or whatever-, not just a different input control. Telling people to try it again but on mobile would probably not make them find such additional value.

I'm sad you took this so personally and so negatively.

genezeta··on Simulator of digging a tunnel through the earth
It still doesn't do much. Mobile version just changes the input controls to using geolocation and motion sensors.

Other than that the functionality is still the same; it doesn't do more on mobile.

← PreviousPage 15 of 19Next →