wst_

Although I generally agree with the concept the truth is it's not easy to stop using `if` or `switch` completely. By applying rules described in the post you are just pushing the problem around. At some point, somehow, a decision must be made which branch to follow. Want to create two methods instead of `if` fine, do it - how are you going to decide which of them to call? You want to use polymorphism, fine, do it - how are you going to decide which class to instantiate? What to use enums with methods on them, fine, how are you going to decide which enum to use? You may say "Oh, I am just deserializing user's input to enum. I don't have to decide." Fine, so you've just pushed decision onto users of your application. Sure, you may use some other methods, especially when you must choose from multiple options (map instead of switch, etc.) but you should always remember - just by avoiding decision making in one place, doesn't mean you've completely eliminated it from business process.

The biggest problem, and biggest fail of IRC. It is too low level and requires people to write scripts when they need anything else beyond simple text message.

I am torn apart here, because I really do like hacking things. The issue is - most people don't. They just want to use it, and they want to use it consistently - no matter the platform, the client, the server they are connecting to. And I totally understand that. More of it, I also understand that if you fail to provide this consistency your service have failed in the design phase and will never get widespread usage.

The sooner we, tech savvy people, understand that, the sooner we'll be able to deliver a successful open services that actually stand a chance with their closed counterpart.

So obviously, give people way to hack, but you must to:

* Design a rich protocol covering needs of the biggest target possible while allowing optionally disable features. Channels history, disappearing messages, embedded media, text formatting, emoji, stickers, web hooks, API for bots, you name it. The protocol must cover most of them, so there is no need to write scripts anymore, unless you need something niche.

* Design a strict spec for the clients, so all of them must keep to the spec, or they fail to be part of the service. And this is critical - do no allow client to behave differently and have a missing features.

* Design clients so they are trivial to use. They must be usable out of box and all (most) of the features must be enabled after installation. Necessary steps to start using it (connection, channels, etc.) should be reduced to minimum and intuitive.

* Keep a community of server and client developers so they can share info and be able to build uniform solution for the users.

* And probably most important - promote the service. And do promote it heavily, unless you want to design something niche, which, I guess, is not what we are talking here.

I've used IRC for years in the past. It was great, I do admit - not anymore. Today I require at least few formatting options (bold, inline code, block code) and no 3rd party tools needed to get anything else work properly. I have no time to hack things I need to use. I would rather spend my time to hack things I like. IRC is just a tool to communicate, I want to use it, not hack it. I loathe to jump here and there to accomplish tasks that should be done within a second with one click.

The biggest problem I observe with many things in the industry is - made by devs for devs. Never for average Joe. Average Joe have no idea about keeping your session attached so you don't loose nick, logs, etc. Neither he cares about that stuff. And honestly - the older I get, the less time I have for this kind of stuff as well. Just make it work or face the failure.

What's the problem? Just setup client to hide images unless you click the link provided - Slack have it, Discord have it. Works exactly the same way, no 3rd party involved. I'm sick when I have to go to imgur to open image and load tons of scripts and see other stuff completely unrelevant. You think imgur doesn't live for profit?

And yet tech hubs are crawling with people who are on the spectrum, and have autistic children. Of course not everyone on the spectrum works in tech industry and not working in tech is on the spectrum, but correlation can be seen.

I think people are overestimating the quality of products they used to call "fresh." Do you know the source of all the products you use? Preparing your own meal doesn't change much, unless you really trust the source.

If I am not mistaken article didn't mention kids age? Anyone knows? I assume above 3 (judging by paragraph about home environment.) The thing is, above certain age it would be very easy to get kids into a challenge and make them to wait. Not to mention that marshmallow may not be a treat for anyone.

Windows: private 90M, working set 111M. Mac: real mem 110 MB, around 10MB shared. Maybe Linux implementation deals better with memory.

So now Foobar2000 is available for Mac? Mister, you've made my day! It's only beta from what I see but I am going to try it anyway. Thank you.

Clementine doesn't use Electron and consumes more of my memory and UI is ugly. Before we start talking about resources maybe we should compare other music players on the market.

Probably this one: https://news.ycombinator.com/item?id=16999407

> Many things are so well crafted here, because of a cultural emphasis on producing things with quality.

I think this, at least partially, is the culprit behind being slow. Quality requires time, years of practice, sweat, dedication and experience. And it works really well for craftsmanship. Japan is well known for it's craft, art, cuisine and aesthetics - even in trivial cases like design of manholes or disposable shopping packages. Unfortunately, the same doesn't seem to work for technology, especially for IT. Learn a language/framework today, forget tomorrow, rapidly switch to more efficient solution, keep up with industry standards and everyday learn something new. There's no place for "learn once - master whole life" concept in current enterprise environment. Maybe with exclusion of basic principles. Everything else change on a daily basis. Yet, Japanese web pages tend to look like messy amateur pages on GeoCities 20 years ago and financial institutions wouldn't change for ages (actually, their online pages looks even worse.)

I do disagree about restaurant lines, though. I've yet to see so well organized crowd. And people do know what to order when they reach the counter because in most places they have a menu in their hands long before they get there. And any other lines, on that matter, especially when you compare Western train/metro stations.

Is it a joke? Well, I'll bite. You do understand how cryptic and unbelievably this sounds to common folks? And even if, as a tech person, I could do such kind of magic I simply don't want to. I believe software must be dead simple to use. If it isn't, it means the designers screwed up their job.

For some time already there are studies suggesting that infant colic is not actually a colic but the process of early brain development. In face of this, looks like there's not much we can do. As much as it is heartbreaking, most parents and babies just have to walk through it.

https://journals.lww.com/jpgn/Fulltext/2013/12001/Brain_Matu...

This is fantastic. Often I am wondering should we start test how good engineers are in asking questions for search engines. I am not going to write the perfect compilable code for them, I have a tools to tell me if I forgot the semicolon in line 31. I don't need to remember standard library 100% and recall all functions' signatures - I have a docs for that. But I should be able to ask meaningful questions that get me closer to the answer and I should do it efficiently. We have tools now, we should start using it instead of memorizing things.

It has a name - micromanagement.

Sorry to hear that. Must be a cultural gap, but I can't find any justification to swear happily in random conversation - friend or not. Not to mention the one that conveys congratulations. If being close with someone is the explanation then, well, I really don't know what to say. There are so many words that could be used instead...

Is swearing, especially saying "fuck you", usual way to congratulate someone in US?

> My psychiatrists have flirted with a bipolar diagnosis but ultimately they think it’s standard anxiety / depression.

I hear that very often, especially from the people diagnosed around 30-15 years ago. I can't get the feeling that this is just an easy excuse to cover inability to find a real cause. I have no study to back it up, just my experience, but I've yet to see a person who has an anxiety just like that. It is an effect, not a cause. You can't treat an effect an just happily ignore the real reason. I am biased by the people I around me, sure, but I would say, very often the cause is being different (even if only slightly) and difficulties to find yourself in the society.

(edit typo)

How that's different in Gradle?

I love Firefox and it is my primary browser for years, on both - Mac and Windows, and it's not going to change anytime soon. Still, I feel Mac version is noticeably slower. Even though I disabled all extensions I can see the difference between Chrome and Firefox on Mac. Sometimes I can even see "naked" plain text page for a moment, before styling is applied (ex: on GitHub pages.)

Video auto play blocking! I can't wait to have that feature. I hope it'll be there on mobile version as well.

I've never saw cherry blue switches in the office but browns, blacks and reds are common. While switches themselves don't give loud feedback, keys hitting the keyboard frame are loud enough. No one makes a fuss about it. Not to mention that not all open space offices are that silent. Mine isn't. Not that everyone is listening to a music but chatter can be heard all around.

I do feel sorry for the guy. I really do. But how is it possible that one guy's tragedy got to the front page of HN? Why everyone's talking about his wife, but not about others, who probably left family and friends in grief the same way.

Means - if you have an address, road name or topography won't help you. Most roads don't have a name, anyways. Not sure about US but in EU it's pretty common that houses are bound to roads so the address encloses road name and house number on this road. In Japan it is different. City is divided in areas, which are divided into smaller areas, all the way down to the building. Even locals often don't know the layout and are unable to tell how to reach the house on next square just by looking at the address.

You mean few small (relatively) communities did this for themselves, because it was obvious no one will think about them and in most cases ordinary user doesn't care much about their input. I am talking about an average map user, globally. If you want global coverage and relying on people to input data, then good luck. I do really like the idea and I wish with all my heart that people would be that generous with their time and effort but we have to face the truth - people don't care, people want a working and complete service. Unless there is some automation in place and free data exchange OSM will never be first choice for general public. Idea is beautiful, execution... Well, Tokyo city, population goes in millions, buildings and addresses not available farther than few blocks away from the train stations. You can see roads but roads in Japan have no meaning. And yes, I could input my house (just 10 minutes from station, blank point on map) but sad truth is, I am unable to input all of them and as you can see - people don't care. They just use Google Maps.

I really don't understand. Looks to me like I am surrounded by different people, then. I didn't caught real RPGs because for some reason it is difficult for me step in someone else shoes but I love board games as well as PC games. The richer story, the better. All my friends are either playing as well, or at least aware about such kind of entertainment and none of them said a bad word about it. Certainly not avoiding the subject. Some of them even meet weekly, old chaps playing board games in a pub. If that's not cool, I don't know what is.

You have to know that Rakuten itself doesn't do much beside the frame. Rakuten is an Internet Mall - a place for merchants to show their products. These people are just sellers, not designers, and they are allowed to customize their products' and shops' pages however they like. Rakuten is to blame for not promoting consistent design among the merchants, but merchants themselves are to blame as well, for tons of noise in the pictures. When you compare, on Amazon pictures are big and clear, while on Rakuten they are there because seller just must put something. Often when you click the thumbnail, you get... the same thumbnail instead big product picture (which makes me mad.) And if sometimes 60-70% of picture space is covered with text. But what really makes me wonder is - how this strategy works? They are there, they are successfully selling their products! It's not only Rakuten, it is visible everywhere on the streets. Posters and commercials are full of noise. Not only text, mind it. It is common practice to have a person with tube in front of your store to praise the products they are selling. Noise is everywhere here. Everywhere except luxurious boutiques. :)

They decided to choose a closed, often tribal cultures for comparison. We can assume they behave as most of us do, mate within the group mostly. So the genes pool/variation differences must be huge between them and Western population (whatever Western means in this context - let's say United States.) On what premises they excluded genetic factor, then?

I found out recently that people too often think about microservices in context of broader solution like it would be one app, just scattered around. I did that mistake in the past, either. The longer I work with microservices the clearer it is to me that teams implementing them should forget about the big product, just focus on the service, as it would be product itself. Assume that anyone can use it, for any purpose they like, as long as they stick to the contract that is, and you'll be fine.

I tend to have two layers of design, now. One - big picture, which treats services anonymously. Just black boxes that respond to input. The goal here is to build solution like kids are building stuff from building blocks.

Other layer depicts services, as separate beings. They treat all their clients anonymously. They have a contract to fulfill and whomever plays by the rules can be served all right. They should be treated as completely separate projects, have their own backlog, release strategies, etc.

Now, if you would have a product that utilize certain data, would you allow some anonymous guy from the internet tap to it directly? No need to answer, I guess.

Edit: typo

Somewhat related. I was surprise to find that building in Tokyo Open Air Museum. http://digitalmuseum.rekibun.or.jp/app/structure/detail?id=s...

> Since lighting equipment for photography was not fully developed in those days, frosted glass was used for the second-floor windows on the north side of the studio for lighting purposes.

I've been there in the rainy day and even then I'd say light was quite OK. I don't know a lot about photography but it was very interesting to see how people solved these problems back in the day.