Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
systemizer
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
systemizer
14y ago
I go to MIT and have taken graduate courses in OS design, database design, and distributed systems. I am more than aware of the issues of byzantine errors, fault tolerance, and replication, etc; however, my post is not about that. My post i
32.
▲
by
systemizer
14y ago
You make good points, and I do agree that multi-platform applications require a general enough server-side interface for many different types of clients. However, you're still going to initially design your application based on a single int
33.
▲
by
systemizer
14y ago
Sorry about that guys. I just started using Blogger's new blog theme. I assumed they would account for javascript-disabled clients, but I was wrong. I'll fix that asap. thanks!
34.
▲
Hacking: Always Design the UX First
(blog.systemizer.me)
68 points
by
systemizer
14y ago
|
35 comments
35.
▲
Building Tweetnode: Popular Twitter hashtags in real-time
(blog.systemizer.me)
2 points
by
systemizer
14y ago
|
0 comments
36.
▲
Show HN: Popular Twitter Hashtags Visualization in Realtime
(tweetnode.com)
7 points
by
systemizer
14y ago
|
0 comments
37.
▲
Web 3.0: The real-time web
(blog.systemizer.me)
1 points
by
systemizer
14y ago
|
0 comments
38.
▲
by
systemizer
14y ago
I think the article is less about "communicating to the user" and more about "which users to target." Should we reevaluate ourselves as developers and build apps that target a larger, less tech-savvy audience?
39.
▲
by
systemizer
14y ago
Does anyone have a statistic on the ratio of apps that are built and require users to understand programming / markup? It would be interesting to see how much we are "plaguing" the software industry by what kinds of apps we create. I'm not
40.
▲
by
systemizer
14y ago
Let's face it, most companies are still built on relational database systems. I'm assuming that a lot of this money will go forward to changing this "culture" and injecting NoSQL into tech industries that have yet to adopt it. ...or they co
41.
▲
by
systemizer
14y ago
Very cool; I forgot about web intents for a while, but this is very encouraging. Who will build the extension to rule them all? Example use cases where file is at an arbitrary URL: 1. Save a file - saves file in your dropbox. 2. favorite a
42.
▲
by
systemizer
15y ago
Just curious: why are you importing so many fonts?
43.
▲
by
systemizer
15y ago
Hackathons are good at creating MVPs. To create something more than an MVP, you need to go out and talk with the users and ask them what they want out of the product. Personally, I attend hackathons because they are fun. It feels great to b
44.
▲
by
systemizer
15y ago
I love this. A lot of my friends talk about creating a website and starting a company out of it, but they are too scared to actually "code." Just the term "code" is enough to scare them away. I wish you good luck in your endeavors and let m
45.
▲
by
systemizer
15y ago
I love computers and I work with them everyday, but I believe the idea of a high school geared primarily towards software engineering is wrong. Computer Science teaches you to think logically about problems. It gives you primitives to build
46.
▲
Quick tips for optimizing performance with jQuery
(jqfundamentals.com)
1 points
by
systemizer
15y ago
|
0 comments
47.
▲
by
systemizer
15y ago
Good point. I think it breaks down to accountability. If you work with 10 people on a project, you are not as accountable because everyone else is responsible for the project as well. However, if you are working with 1 other person, that pe
48.
▲
by
systemizer
15y ago
Building an online community is difficult . If anyone has good research papers that have analyzed online communities and has successfully predicted the culture of an online community at its inception, please let me know.. Online communitie
49.
▲
by
systemizer
15y ago
If you're in a startup that is up for trying new things, I think having a group of developers working together on these resolutions would be a great idea. Let them take 5-10% of their time during the day to work towards these resolutions. H
50.
▲
by
systemizer
15y ago
It's important to get your hands dirty and do a bottom-up approach, but it is equally as important to think top-down as well. What I mean is don't be ignorant of the "gold plate" while you are creating the minimal viable product, but be fle
51.
▲
by
systemizer
15y ago
hrrmmm, It might be MITM. Looking into it now.... thanks for the help
52.
▲
by
systemizer
15y ago
This is what I am getting: http://imgur.com/lnbBw
53.
▲
Where did reddit go?
(reddit.com)
3 points
by
systemizer
15y ago
|
3 comments
54.
▲
by
systemizer
15y ago
I feel like there must be a better way to do this... you are all asking for spam. It only takes one recruiter to come along, add himself to the circle, and go nuts with offers. Oh exception case? I think not.
55.
▲
by
systemizer
15y ago
I'm going to have to disagree. As a developer, I would highly prefer having my co-developers in the same building, if not the same room with me. It's about having that certain "hum" of energy in your environment that you can only achieve if
56.
▲
by
systemizer
15y ago
The CSS code isn't confined to a namespace, which could be a problem. For example, I might want to use .rounded for a global CSS style rather than it refering to only progress bars.
57.
▲
by
systemizer
15y ago
However, you have to careful about reading books on technology. It is very possible that the technology has changed since the book was published. There are some technologies I would read books for and some technologies that I would read the
58.
▲
Karma-based communities lack innovation
(systemizer.me)
1 points
by
systemizer
15y ago
|
1 comments
59.
▲
by
systemizer
15y ago
The idea using next() with asynchronous sounds interesting. With sugarless, you could create a state machine with functions as the nodes and next() calls as the transitions. I don't know if I would ever use this, but it is still an interest
60.
▲
by
systemizer
15y ago
So true: 1. Some of the greatest inventions were found out by mistake. 2. If you don't take risks, you will never know what is possible. 3. If you always follow the rules, you constrain your domain to what is already discovered and underst
More ›