Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
russelluresti
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
27 ms
·
211.
▲
by
russelluresti
14y ago
After reading the comments, I think a lot of people are getting hung up on the implementation aspect of BEM using XML/JSON to determine markup and such. From what I can see (and this is just my take on it), the BOSS project doesn't require
212.
▲
by
russelluresti
14y ago
BEM, to me, comes in two parts. There's the CSS naming conventions and then there's implementation. I dislike the implementation of BEM using XML or JSON, I think it's kind of obscure on how everything works. However, I do like BEM for the
213.
▲
by
russelluresti
14y ago
Freelancing is all about relationships. If a possible client is looking for a freelancer to complete a project, the only difference between Developers A and Developer B is their price (because, the client isn't going to understand the skill
214.
▲
by
russelluresti
14y ago
You're right, I did misread your reply - I originally thought you said it was innovation that took laboratory time. Though, now that you've explained it further, I'm still not sure I agree with the concept. Pure research follows a specific
215.
▲
by
russelluresti
14y ago
First, this isn't Bret's introductory article on this topic. As far as I know, his first talk about this came in January of this year (watch the Inventing on Principle video on Vimeo). Granted, 7-8 months isn't a super long time, but he has
216.
▲
by
russelluresti
14y ago
It's amazing how many people have a problem with the idea of testing a solution. I'm simply saying that assumptions need to be challenged and assertions need data to back them up. I'm not saying any of this ideas are inherently wrong, I'm s
217.
▲
by
russelluresti
14y ago
I disagree that real-world innovation isn't tested, iterated on, and improved. Look at flight and the Wright Brothers. They didn't just run numbers and present ideas. They built prototypes and tested their assumptions. That's what Bret need
218.
▲
by
russelluresti
14y ago
I'm well aware of qualitative research, but he doesn't even have that. And, while I agree that you can translate and interpret the major themes, all you have done at that point is recognize that you have a similar problem and have formed a
219.
▲
by
russelluresti
14y ago
I disagree with the idea that proof of those concepts translates perfectly across all situations. You have to test something before you know if it works or not.
220.
▲
by
russelluresti
14y ago
This doesn't make sense, because the UI design of the iPhone WAS tested. They did a ton of research into their solutions. They did exactly the type of testing I'm advocating.
221.
▲
by
russelluresti
14y ago
> Brett Victor is pointing out what he perceives to be valid flaws Where are the numbers? Where's the testing? Where's the proof that his proposed changes are more effective in teaching a new programmer? Validity comes through numbers,
222.
▲
by
russelluresti
14y ago
Here's my issue with the "advancement" that Bret is doing. It's all conjecture. He has no product. He has no users. He has theories. Theories that sound good to you and me, but, ultimately, theories that are untested and unproven. There's n
223.
▲
by
russelluresti
14y ago
Not to take away from Bret's ideas, because they're great, but here are my responses. 1. I'd say that there's a significant difference between Bret and Linus. Specifically, when Linus believes that developers need better tools, we get git.
224.
▲
by
russelluresti
14y ago
Link bait and wrong on every point. This article is a waste of time to read. On each point... 1. Where's the proof? Where's the research? The usability studies? The group surveys? There is NO evidence presented to support this point. It's j
225.
▲
by
russelluresti
14y ago
I... what... you need to give me back the time I wasted reading this post. You talk about product demos, learning tutorials, and demos. These are not all the same thing, and have different use cases. Remember that not everyone learns the sa
226.
▲
by
russelluresti
14y ago
Without seeing your CV or code examples, it's difficult to tell where the main areas of concern may be. And that's if there are any areas of concern at all, you could just have hit a streak of bad luck. But, I will tell you something I've l
227.
▲
by
russelluresti
14y ago
I'll have to see what this is like by actually using it. Right now, my biggest concern is that it usually makes for better usability if you allow the user to organize and group content in a way that makes sense to them. I don't feel this is
228.
▲
by
russelluresti
14y ago
If you wrote this for the "learn to code" people... here's an issue... You ask several questions of the reader: "Do you attend Code Retreats? If you do, do you actually write code or do you watch the other guy?" "Do you create Rails Gems or
229.
▲
by
russelluresti
14y ago
The idea of pulling existing video or interactive learning resources into one location is interesting, but there are definite improvements needed. First, people looking to learn things often do not know what is required of them, that's why
230.
▲
by
russelluresti
15y ago
Very cool idea. Will you be offering a forum or board so people who are taking the same course (or have taken the course) can talk to each other / ask questions? Also, sign up seems to be down.
231.
▲
by
russelluresti
15y ago
First: Pricing is set too low; margins get squeezed. Fundamental flaw: eBooks have lower production costs than print books, so their prices should be lower. The article mention "warehouse space" as a constant cost, but if the purchase of ph
232.
▲
by
russelluresti
15y ago
I felt the same way. There was no information as to what the product actually was, so I just left at the first screen. Like you, I assumed it was an attempt to game HN.