HN user

ooqr

217 karma
Posts1
Comments110
View on HN

I turned off syntax highlighting long ago. You may find you don't need it.

You either understand the code or you don't.

2D Syntax 9 years ago

Surprisingly exactly what the title makes it sound like. Very cool!

I'd go so far as to not only agree with your assertions of the best points of Rails, but to also extend your skepticism of the excellence of Rails' templating to calling that the worst part of Rails. Of course, one can use Rails as an API only service and it's quite adept at that.

That's exactly what I'd like to see. The problem with UBI is it's not that.

There's room for more than one social program in dire circumstances, but ideally we should have a social structure which incentivizes doing good. Help those who can't help others, and encourage those who can to do so.

You're very much missing the point. There are lots of jobs that used to exist that are no longer viable. This happens. The fact that people are unemployed is a separate issue from any given job no longer being viable. And yet there's plenty of work that needs doing.

Be realistic about point a).

And for point b), it's always truck drivers brought up in these instances. Yes, think of the poor truck drivers. I'm sure they love doing a dull job.

If a job is replaceable by machines, it's not worth doing.

I get the worry that people will be without livelihood, but it's not as if this world has a shortage of work to be done. If we had no more work to do, sure, bring on the UBI. But we do. Clean litter out of forests, plant new forests, visit the sick. Whatever it is, there will absolutely be more work for humans in the future. People not being forced to drive trucks means they could be doing something else more useful.

And if people lament losing a particular job and having to pick up a new one, well, sorry but that's reality. I could just as soon lament not getting paid to doodle cartoons.

I'm absolutely not saying this is an easy problem. I also agree with your last point. I'm being idealistic, I know, but I'm cautious about accepting any proposed solution.

I definitely see the merit in comparing the US to Europe in terms of what has worked. Even as I am cautious, I value societies willing to experiment and progress forward with solutions to problems.

I'm not sure the US system is amenable to the same thing, but I'll bow out at that point and merely listen to what others have to say.

What I do suspect is that the landscape is changing with regards to what jobs need a degree and how easy knowledge is to obtain.

That's still time opportunity cost for the student and merely shifts the financial burden.

I'm not against a liberal education for the betterment of the person, but it's not a sound investment.

We should not aim to make college free by means of government sponsorship, but rather education free or inexpensive by means of lowering the actual costs. As someone else said in this thread, certain kinds of knowledge are rather cheap to be had. Yet even so, degrees are pursued blindly by students, and hired blindly by employers.

Again, there's plenty of benefit to schooling. I liked taking classes with peers, including the non-major classes (for the most part). But throwing more money at the problem is the problem.

In spite of what you see on TV, it's not up to a victim to decide whether or not to press criminal charges in the end. That's up to the attorney general usually.

It's great that this was part of an assignment. Git is a fantastic, incredible tool. Along with testing, it's one of the skills I figure is just as important as the things you learn in university, but which typically isn't taught there.

I think Rails does a pretty good job of making well-documented sense. Lots of crappy gems abuse things like implicit global variables, rewriting core methods, and other monstrous applications of metaprogramming.

The problem as I see it is when metaprogramming is used laterally or vertically. If code at a higher scope changes code at a lower scope, this makes a lot more sense than the arbitrary and profane directions of mutability that Ruby allows. So, like all things in Ruby, it's a matter of how the tool is used.

To metaprogramming! The cause of -- and solution to -- all of life's problems.

Fair point about my word choice. I just think we can do better is what I mean. I think I agree with you, but I'd need to see it in action. Currently I just use workspaces for whatever I'd use stacking for.

I've used Amethyst day-to-day on my work laptop for several months and overall I'm happy with it. It's a bit idiosyncratic, but that's more the fault of Apple for not making it easy to develop such a plugin.

It's strange that a company focused on good design and ease of use is beholden to ancient window management traditions such as manually dragging every single window into the dimensions you want. When you open and close terminal windows to various servers dozens of times a day, need a window open on the side with a site showing documentation on this or that, it just doesn't make sense to waste time doing something that could be automated.

I find the most valuable point is the last: whereas, sure, you can go on wikipedia and find dependencies of an area of knowledge, that three of prerequisites makes more sense to be presented as a flow converging on a point, rather than having to dig deeper until you find a node you already understand.

A suggestion for your product: build these dependency graphs automatically, and let users mark subjects as already satisfied. That way you can omit digging into dependencies that are satisfied. If you really want to be righteous, recursively mark the dependencies of the satisfied dependency as also satisfied. That way a user can pick a topic and find everything that still remains to learn to get to that point.

And you can have the best of both worlds. Generating a linear progression of things to learn becomes a simple matter of printing the dependency tree in postorder.