640 karma · joined August 25, 2016
If your function returns pizza, as mentioned in other comment, adding some toppings won't change the boundaries. It still returns pizza, with peperoni or not. It doesn't change how you make the pizza. You're just adding more data to it. You may solve it with syntax, language data structures, etc. Whatever you like to make it more readable to the caller. But probably you'd want to pass toppings in arguments.
On the other hand if you have a boolean param that changes how function works. That's questionable in my opinion. Say you want to return list of users from DB but omit interns, sometimes, and you need to call API (or query DB) to know if someone's intern. You could define `omitInterns` bool argument but it seems clunky to me.
I may be mistaken, though. As said: defining boundries is not easy.
This also touches other problem a bit. Should we strive to decrease `if` branching in our functions or not? I personally tend to branch very early on, so later I can follow straight path. That's not always possible, but if it is, it helps greatly. Makes code easier to follow.
Two people who changed my life forever - Sir Clive Sinclair and my Father who'd been bold enough to invest in Timex 2048 despite price and difficulties of life behind an iron curtain.
Thank you. Both of you.
Quoting the article:
> Қазақстан Республикасы, will henceforth be rendered Qazaqstan Respy’blikasy.
But cyrilic "у" suppose to be latin "u". So it should be "Respu’blikasy". Wikipedia [1] seems to agree, too, according to table from January 2021.
[1] https://en.wikipedia.org/wiki/Kazakh_alphabets#Latin_script
Those events are massive. Usually police force is involved to steer the crowds. Streets are closed. Disruption everywhere. But, oh boy, it is so worth to sacrifice convenience to see the show. I've had occasion to see three and that was fantastic experience. Show in Nagaoka, in Niigata prefecture was the biggest and the most colorful I've seen in my life (not that I've seen many, still) and the execution, sync with the music, was flawless. I must thank my Japanese friends who booked the trip for us all. Otherwise I would miss it for sure. The two others not worse a bit. One next to Sumida river - the biggest one in Tokyo - and the other in Tokyo too, next to Futakotamagawa station. Both spectacular.
One other aspect of any bigger events that always amazes me is how safe and organized they are. Everyone is drinking hard during many of those and still no one argues, no one is aggressive and no one steals. That's a digression, though.
If you look around there's plenty of such a "pointless" jobs. The same with people steering the traffic at the parking lot entrances/exits at any bigger entertainment or shopping center. Sometimes with almost no pedestrians around and yet those people are standing there in sun or rain alike. Or people who's only job is to smile and open doors for you, less common, but happens as well.
To be honest, though, as a "consumer" of such jobs (pedestrian in this case) I do feel they took an extra mile to make it as safe and comfortable for me as possible. And I do feel better about it.
It may look pointless at the surface, but I think those jobs are extremely important for society at large.
I work quite a few years in IT and never, during any interview or meeting, I've been introduced as anything more than just an engineer. This must be cultural gap, no doubt, but I'd feel weird if someone would detailed my career in front of other participants. Of course I have nothing against filling some details in by myself but only if applicable in given situation. Truth to be told I've never worked in Australia or US, but I did some job in two EU countries and in Japan and, as said, never encountered detailed introduction.
Is this still a thing?
Now, I do get that there's a lot of people who don't like spending time at home for interview tasks but when you think about AND it's not skewed to extreme (say, big task 8 working hours worth) then, in terms of time wasted, it's not such a big difference. Interviewer can then see the code quality, can talk about it with candidate, clarify some missing pieces or pitfalls found, etc.
IMHO most important is not if the candidate knows how to solve some hard or even medium problem when I speak to them and they are stressed enough already. What is important is if they're willing to learn, if they know how to search for stuff they may not know and if they can produce performant enough, but excellent to read, code.
Living in couple of countries In EU and Asia, I can't imagine not knowing total price up front. It's pushing legislation problems on the end customer.
If you think about it, how well did you speak your native language at 4? How well at 7? Did you attend any classes to teach yourself? No, I assume not. So how come you are fluent?
Turns out, it is all about ingesting as much as possible. Even if you barely understand at the beginning. More of it - learning grammar is just a distraction. You can skim the book to have an overall grasp of it, but that's it. You weren't learning your native language grammar by the age of 7, did you?
The key is to ingest comprehensible input. If you can't understand the sentence, have a visual cues. Start simple by learning most frequent 1000 words (should take you 2-3 months max with Anki) and then you can easily switch to sentences. Just keep your senteces at the level that you understand almost everything but a word or two. One word ideally.
Read or watch only context you like, you are interested in and you have fun with. That's it. Do it long enough, every day, and you are set.
As an example, I've been learning Japanese in class for 2.5y and could not read nor speak as well as I'd like to. Not to mention I couldn't read kanji at all. Now after 9 months of trying language acquisition I can read children books (Winnie the Pooh) and comic books. If that's not a win, I don't know what is.
This is interesting observation which doesn't go in par with mine. From my experience, native English speakers have really bad pronunciation as the Japanese is full of "soft" sounds like shi, chi, ji. Those are missing in English. For example when you want to say Shibuya, the first two letters should not be pronounced the same as in word "shell." The same "j" in kanji should not be pronounced as in the word "jam." I find this quite common among native English speakers.
On the other hand, I find people of central and east Europe the most gifted. At least WTR pronunciation. They got used to the most of the sounds spoken by Japanese and some more. Some subtlety aside, of course - it's not 100% the same, but close enough.