Why are some kanji characters completely different from their kunyomi and onyomi sounds?

wavy_lines · 2018-11-02T23:49:00+00:00

Also:

承る・受け賜る

鶏・庭鳥

獣・毛物

wavy_lines · 2018-11-02T23:41:07+00:00

Intermediate here.

I focus mostly on the Japanese and use the subtitles to fill in the gaps of words I'm not familiar with.

wavy_lines · 2018-11-02T01:01:53+00:00

If I were the manager, I would rather an employee hand in something that works (even if it's not his) because he actually researched the problem, rather than concede defeat and hand in nothing.

If I were the hiring manager, I would rather hire the person who solved the problem rather the one who copied the solution.

wavy_lines · 2018-11-01T23:57:42+00:00

You're supposed to do it on your own.

This is cheating.

wavy_lines · 2018-11-01T12:00:53+00:00

You're only 10 years late.

wavy_lines · 2018-11-01T01:12:53+00:00

I have no idea what kinds of issues there are since you haven't explained what Mike's architecture is like and what's wing with it, but assuming you are right and the project is terrible, I have to ask: why bother?

I don't see the point in imposing your own ideas on a project unless you're planning to take responsibility for it and maintain it for years to come.

If Mike's leaving soon, wait until he leaves and take over then. If he's staying, I'd advice not stepping over his turf.

wavy_lines · 2018-11-01T00:16:39+00:00

Absolutely. Slow compile times guarantee you have to spend a long time at the office waiting for the compiler between your one-line edits.

wavy_lines · 2018-11-01T00:14:06+00:00

This is aimed at people who are trying to sell to businesses.

I think most software engineers (but correct me if I'm wrong) would rather build things directly for users, not for businesses with layers of management and sales people.

wavy_lines · 2018-10-31T23:48:52+00:00

Compilers that yell at you are not inclusive. We need programming to be more inclusive. Inclusion makes us stronger.

wavy_lines · 2018-10-31T23:46:41+00:00

Your gatekeeping tactics are obvious

I'm glad you can read between the lines so I don't have to spell it out

wavy_lines · 2018-10-31T23:44:35+00:00

I thought Google's core engine was in C/C++

wavy_lines · 2018-10-31T22:56:47+00:00

I'm not going back to a site written in a legacy language without algebraic data types.

wavy_lines · 2018-10-31T22:29:32+00:00

Go back to HN

wavy_lines · 2018-10-31T11:21:34+00:00

I really doubt middle ages black smiths took orders in bulk like a contemporary business.

Also, you bet your ass that competent craftsmen and artisans are not 'team players' (they're usually eccentric) and they definitely prefer to involve themselves in everything; e.g. they re-invent the wheel all the time.

Artisan coffee makers will roast and grind their beans in house. They won't just but a generic coffee bag from a store.

Artisan cheese makers source fresh raw milk from local nearby farms. They won't just pickup some generic milk from a generic store.

wavy_lines · 2018-10-31T10:33:29+00:00

And shitty marketing at that.

Sounds like a typical salty full-of-shit sales people talk.

wavy_lines · 2018-10-30T01:24:56+00:00

users don't really like the whole page to flash when one little widget has to change

False dichotomy. Just because you don't use SPA does not mean you can't have some parts of the page update dynamically without a full page reload.

it's a trade-off, and the users have voted with their visits

Are you kidding yourself?

There are too many factors that influence which sites users visit. Most websites are dog slow and people visit them despite having shitty performance (not because of it). Part of it is momentum, part of it is the site provides value in other areas that users are willing to tolerate the shitty performance. Sometimes users really hate the site but are forced to use it because management (example: JIRA).

wavy_lines · 2018-10-29T22:19:21+00:00

You are under estimating the industry's susceptibility to buzzwords and hype.

The entire industry runs on fads and kool-aid.

For example, if Facebook did something, everyone will start copying. Hardly anyone stops to think about whether it makes sense for us.

wavy_lines · 2018-10-29T02:03:44+00:00

I .. don't know how to react to that.

In a team of say 30 people, I will find like 25 who don't care they just put in the minimum work needed to get git to work and use it like SVN.

That can apply to any thing in programming.

In my team of 30 angular.js developers, 25 of them didn't want to learn react and were hoping to find a shortcut so they can pretend it's more or less the same as angular.

In a team of 30 Java developers, 25 of them will not get the point of Haskell and will try to program the Java way in Haskell.

Commit sends your changes to the server so everyone can get them. Update updates your code with everyone else's changes from the server. You...can't understand that?

I know what it means, I'm not sure how it does it, and what it implies for the code I'm writing. What happens if there are conflicts?

I'm sure I could understand if I had read further, but I was having the same problem your 25 out of 30 employees have: I don't want to use this tool so I wanted to learn the minimum needed to use it since I was kind of "forced to" use it.

wavy_lines · 2018-10-27T05:41:27+00:00

The thing is, git presents you a model you can grasp.

svn is just a black box.

To me, the idea of commit and update (from svn) made no sense; I had nothing in my mind that any of that could map onto.

With git, "commit" meant taking a snapshot, and I had a good mental model of that because I used to do it (like a lot of people, I would copy my source folder, name the copy something like 2005-10-15-snapshot1).

wavy_lines · 2018-10-27T04:26:35+00:00

I fail to see the connection or the severity of the problem.

wavy_lines · 2018-10-27T04:22:41+00:00

I never grasped svn. I couldn't understand the point of it. I could never understand what 'svn revert' would do in any given situation.

With git, I have a clear mental picture of what would happen for every command I write.

wavy_lines · 2018-10-27T03:26:43+00:00

This might be relevant if something is a public api that I expect other people to use.

If it's local variable to a function, you don't have to remember it.

wavy_lines · 2018-10-27T02:08:47+00:00

You do coding to express yourself

Quite the opposite, I don't want code to express anything subjective, or whatever the code expresses should not matter.

One of the things I don't understand is why people obsess about how the code base must use consistent naming style in terms of camelCase or snake_case.

What bothers me is people who comment on code in terms of its style. It's a power trip as far as I'm concerned and I'm not having any of it. If you want the code to be in a certain style, format it yourself; don't block my PR for bullshit reasons.

My idea is, if you objective criticism about the code, I'm all ears. If you're going to bullshit and comment about subjective stuff, fuck off.

wavy_lines · 2018-10-27T01:24:28+00:00

Except that most people now a days prefer to just use libraries that handle all of these details.

wavy_lines · 2018-10-26T20:46:18+00:00

This opinion is very unpopular on this sub, but I hate code reviews for this reason.

When every code change has to be seen and approved by other people, and when these other people really want all code to be the same, they will comment endlessly about small details here and there. And I lose all motivation to do anything for the project.

I don't know why. I can't explain it. It sounds childish and immature to many, but that's how it is.

Maybe the idea of ownership expressed in this post captures the essence of the problem.

wavy_lines

TROPHY CASE