synnik

16 ms·

121.
by synnik 15y ago
I hate it, too. But hate it or not, this is reality in the corporate world. Knowing the correct technical answer is nowhere near as difficult as getting the powers-that-be to agree with you. For small startups, perhaps you can stamp it out.
122.
by synnik 15y ago
Any job seeker who is worth 100K+ won't pay the subscription fee anyway... their listings show the location and often the company name, even to non-paying users. It doesn't take much effort to figure out how to go find the actual posting di
123.
by synnik 15y ago
I don't buy the skill set -- It is way too broad. Some of those skills must be stronger than others. I have no way of knowing if you are a CSS wizard who also does some C#, or if you spend 90% of your time doing GIS apps for iOS. And I ther
124.
by synnik 15y ago
Cost is often a perception thing. For example, I work in a mostly outsourced IT shop - the only thing in-house is our custom coding. With a $100 million annual budget, the difference between free version control or $200 for FogsBugz license
125.
by synnik 15y ago
I'm amused that a UX article has such a poorly written headline that I had to read it 5 times before I my brain parsed it properly.
126.
by synnik 15y ago
While this is a decent article to stimulate thought, it has too many details to be taken totally seriously. There is a significant vibe of : "Do it like me, or else you are a fraud."
127.
by synnik 15y ago
Above the break: A gaudy menu and ADS! Nothing but ads. Below the ads: whitespace. After the break... I only noticed there even WAS more content when I saw how large my scrollbar was.
128.
by synnik 15y ago
There is a huge logic gap here. He is comparing 11 characters passwords to 6 character passwords. The difference in length also will account for a significant difference in the time required with brute force. I think what he is trying to sh
129.
by synnik 15y ago
So what you are saying (whether you meant to or not) is not that it is impossible to become a pro in 10,000 hours... but rather that your training has be to be focused on what "being a pro" really means. If he were to integrate your exact p
130.
by synnik 16y ago
"should be able to do work worth about $3 million a year." Note that he says you can DO work WORTH $3 million. That quote says nothing about actually selling that work, or getting it in the first place.
131.
by synnik 16y ago
Noted. Consider my point undermined.
132.
by synnik 16y ago
The problem with the Microsoft stack is not technical -- it is financial. Why pay M$ license fees when other platforms are free? Especially as you scale?
133.
by synnik 16y ago
France has a long history of security-limiting policies. I don't know if it is still in effect, but at one point in the 90s, they did not allow software to have better than 40-bit encryption. In turn, American software companies had to writ
134.
by synnik 16y ago
Keep these points in mind when generating error messages to your end users.
135.
by synnik 16y ago
The name might need work. When skimming the HN front page, I thought it said: "Annoying small web server..."
136.
by synnik 16y ago
My initial startup was a CMS product in 1999. At the time, there were few players, and few open source products. We were able to charge from $25,000 to well over $200,000 per implementation. We even had one contract for over a million to do
137.
by synnik 16y ago
I'd recommend y'all not worry too much about the inaccuracies of his historical contexts. He actually gets to his point farther down in the article, and his point is valid.
138.
by synnik 16y ago
Even the great Hari Seldon was unable to accurately turn mathematical models into true predictions of human society without the intervention of R. Daneel Olivaw.
139.
by synnik 16y ago
I have always supported a philosophy of patience when it comes to being right. When entering a new organization, make your case(s) known, but don't push them. If you are proven to be often correct, over time people will see the pattern, and
140.
by synnik 16y ago
You also could adjust your focus... instead of telling us all how you are being blown off, figure out WHY. Even if they are all wrong, something is giving that incorrect impression. And you will have a hard time recruiting others to your ca
141.
by synnik 16y ago
And immediately following that quote: "so if you have good reasons not to change anything that’s fine" It sounds like they expected nothing and this was a CYA email, knowing TechCrunch would not comply, but allowing them to say, "We tried."
142.
by synnik 16y ago
My username was 100% unique from 1991, when I first started using it, until some time around 2005. (At least according to veronica, then altavista, and now google.) In the last 5 years, enough other people have picked it up that the only fr
143.
by synnik 16y ago
No -- I am arguing that alignment, consistency, appropriate typography, non-mediocre use of color are only NOTICED and cared about by 1%. Overall usability is what the other 99% care about. And should be of primary importance. Saying that o
144.
by synnik 16y ago
This focuses heavily on the wrong side of the 10% rule: For minute details on ANY creation.... only 10% of people who see it will notice. And only 10% of those who notice will care. If you've got the time and energy to keep that 1% happy, g
145.
by synnik 16y ago
We use customized TFS Build Processes. Really, working in the Microsoft stack is not something to do halfway - either avoid it like the plague, or embrace it and use all their tools.
146.
by synnik 16y ago
While I'd love to agree, reading someone's code does not tell you: 1) If they actually wrote all of it, or if it derivative of someone else's work. 2) Whether any particular function took them 10 minutes or 10 hours. 3) What options they co
147.
by synnik 16y ago
And we would politely end the interview and not call you back. Questions like these are not made to decide who to hire -- They are made to establish a base level of competence. The ability to answer these questions does not prove anything.
148.
by synnik 16y ago
Yes, there is a difference, and it is not meaningless. Let's go with your example. You don't touch things that cause pain. And you think that hot stoves, fire, etc cause pain. But what if people show you the trick to walking over hot coals?
149.
by synnik 16y ago
There is a difference between learning from your mistakes and using the same algorithm on an updated data source.
150.
by synnik 16y ago
It works very well if you establish a true partnership. Our local employees do the design, strategy, and thought leadership. An on-site team from our partner sit face-to-face with us to be sure we have mutual understandings and good communi

More ›