It's a refreshing way to end the week, and if everyone is doing it, it doesn't seem like a 'burden' or a lack of productivity.
It would be hard to just implement this if managers aren't on board with the idea, but try it out one Friday a month. If it starts working well, bump it up to two, and hopefully you'll get to every Friday.
Here's link about 3M's 15% time - http://www.fastcodesign.com/1663137/how-3m-gave-everyone-day...
- Good balance of page elements, such as copy over graphics, etc.
- Legibility of text (this is the visual spacing of which text can be read, font-size, colour, line height, line length, kerning, etc, etc).
- Readability of text (does it make sense when you read it?)
- Professionally written copy. Forgets saying "We are the leading company in ..." - yeah you and everyone else. Tell me why you're better, not that you are better, and why it's important to me, not your "thousands of other customers".
- A strong value proposition (why am I here and what do I get out of it)
- Strong images, such as good photography with people in it (pictures of people do wonders to user engagement). Also have them looking at the product or where to go next as it guides the user.
- Page load speed - I don't want to see the non-essential elements be rendered first all waiting while those adverts and analytics are loaded before I get to do anything useful.
- A business identity - professional web sites are run by professional companies who don't mind talking to you over the phone, so show the phone number.
- Clear navigation with no confusing terminology that makes me wonder if I'm in the wrong place.
- No tacky animations, just non-obtrusive complimentary motions that support my visual comprehension of the action I took, rather than it just trying to look flashy.
- If it's a service (such as MailChimp), then don't be shy of what other big brands use your product. It gives more credibility.
- Consistency. Keep navigation, fonts consistent with their purpose.
- Be honest. When it comes to pricing, don't hide it and make me call. Otherwise I think you're up to some shady practice to hound me in to spending more.
Okay, that's all I've got time for.
You can make a turd look like a professional web-site with enough polish. But even if you do that it is still a turd.
People will come to your site if it has great content even if it doesn't look "professional." Polish just makes them more likely to stay but not really more likely to return (content does that).
Polish is all about getting both the "big" things right but also about getting the little tiny details right too. If you spend hours considering if your site should have rounded corners on the CSS boxes then you're doing it right...
You often don't have the time to read through hundreds of pages of programming books, and I don't have the patience for that anyways. The best way to learn is practice, practice, practice. You practice programming and you practice your "look up" skills for finding new info.
For me, I learn most when I create something or put my learning in practice immediately. Whether it's languages (natural or programming) or a certain framework, or paradigm. The key is that by running into problems you see how a piece of technology fits into the big picture.
I would not worry about too much competition. I would rather look at how much piece of the pie is potentially available (depending on the answer to the question about market size above). For example, you say that there are 5 national competitors for that particular idea you had but locally, there might be opportunity. So why not start local and talk to your potential customers ? Again, depending on what your target audience is and their market size, it could be very likely that there still is a big piece of the pie left for you.
I would recommend not talking to random people. Talk to people who are in your target market instead. And don't just ask if it's a good idea. Ask them if they would want to pay $X per month for it.
Warning: parse_url(http://) [function.parse-url]: Unable to parse URL in /home/content/89/7601089/html/pitchback/functions.php on line 58The company "" is already in the pitchback.me system. If you believe this is an error, please contact email@example.com
There is a monthly Freelancing thread on HN, on the 1st of the month
2. Click on the usernames.
3. Write down email address from their profile.
4. Send the following email to the list of people you wrote down (at least a 100, because if you get a 2% response rate, you might get a gig out of half an hour of work):
My name is $name, a freelance developer. Read your comment about $subject, and I think you make a good point. Anyhow, just dropping by to chat a bit about what you are currently up to. Hope you are having a great day.
Then just get a conversation going and talk about what you do. Simple.
- http://beautifuldocs.com/- https://readthedocs.org/
1) It's self contained. No dependencies on third party OO libraries or frameworks.
2) The code is very readable.
3) It's a canvas library, so it's fun to work with if you're into graphics and visualizations.
4) You'll learn a lot about how many JS projects are built, documented, and tested, if you get it to build and the tests running on node.js.
Here is what I would do:
1) Check out the project and get it building.
2) Read all the files in the util folder. You'll see a lot of methods added to Object and Array.
4) Then take a look at the base class: https://github.com/kangax/fabric.js/blob/master/src/object.c... and an inherited class: https://github.com/kangax/fabric.js/blob/master/src/line.cla...
5) Search for instances of the "bind" method, and see how they're used.
Finally, this is just a personal opinion, but I don't like Crokford's chapter on OO JS. I just don't think it presents your options well. If you decide to write a large project in JS using OO techniques, I think you'd be better off utilizing an OO library, compiler, or framework like TypeScript, Google Closure, Prototype or CoffeeScript, than you would charging forward armed with Crokford's chapter on OO.
As far as print goes, you'll want these books in your reading list:
JS The Right Way: http://jstherightway.com/
The next step should be to contribute to some open source JS frameworks. I will suggest jQuery or YUI. You need not always write code, you can begin with improvements to the documentation and later move on to submitting actual code.
If you write a lot of js, you'll probably write messy js, but you'll understand how it can so easily get out of hand.
Then read a lot of code and the other resources people have linked to here. Having done a lot from scratch will motivate the solution a lot more.
You will have actually run into the problems they are telling you to solve and understand why it's good js rather than just taking their word for it.
Very well written, well explained, and it points to many more best practices.
I assure you, its worth the money.
Note: I am in no way associated with the publishers or author apart from being a beneficiary of this awesome repository of knowledge. This is not even an affiliate link.
There are lot of examples which will teach you great stuff.
That means you should only learn from people who recognize how broken js is, and thus of course js: the good parts sounds like the right direction, whereas I think Resig is a religious zealot and shouldn't be listened to (the guy actually thinks broken js as a first language is a good idea).
Lastly, js is broken in many ways, don't use it when you don't have to, that means avoid node.js and use a good server side language instead.
tl;drjs sucks, don't listen to people who don't ack that, learn to avoid the sucky parts instead.
And more downvotes from the zealots... HN is so predictable these days.
I also own and operate the site and the app.
I've looked at Thycotic Software's Secret Server product (http://www.thycotic.com/products_secretserver_overview.html) I was impressed, but none of my consulting customers have signed-up.
I recently spun up a copy of the open source WebPasswordSafe (http://code.google.com/p/webpasswordsafe/) and liked what I saw but haven't really had much of a chance to bang on it.
Wearing my security auditing / pentester hat I've run into CyberArk's Enterprise Vault product (http://www.cyber-ark.com/digital-vault-products/pim-suite/en...) and found it very reasonable. It was refreshing to do a pentest where we didn't find a shared Keepass database or something similar.
IronStratus is another one to check out lets users keep their own personal passwords and grant access to apps passwords by an admin.
I personally prefer 1password - but it's really single user oriented.
Obviously different from I'd/auth providers like okta or ping identity...but i find there are so many accounts/passwords shared in organizations for services that these guys may not support. (apps with no SSO services for example). Yes, they have some password management tools but they don't seem to have in app/browser shortcuts (ie:chrome/ff extensions).
I've seen some companies hack a homemade solution based on Truecrypt as well, though it's probably not very efficient.
Elance (http://elance.com) is a good option generally for finding contractors.
While they are spendy, design-focused recruiters like Creative Circle and Creative Group can help you find both contractors and full-time employees. They do a decent job of screening so you only see qualified applicants, unlike Elance and 99 Designs.
Whenever you come across a designer you like they are usually more than happy to perform further work outside of design contests.
Why did you make this a self post instead of a comment?
It's my 10x better test. In general, I think all three are good to know, and each are good at what it does. Ruby is in the 'everything is an object' world, and does it well. It optimizes for programmer speed, rather than execution speed.
Node.js is like being dragged halfway to lisp and functional programming. Learned a lot here, but having callbacks is almost like having to program with continuations all the time.
Go is for systems programming, and it's got its own take at concurrent programming. It's worth looking into.
Either way, just start at one, and eventually do side projects in the others. Can't hurt to know them all.
Last a note about Ruby, I think the VM is amazing the API is great and programming in ruby you can throw things together blazingly fast and clean, so its also a good choice. Overall though I'd say Go, I think its the best language to come around in a long time and people will adopt it
Node is better for streaming/real-time applications. You can build any type of web app with it, but it's best known for chat/real-time stuff.
That said, I actually love Node and plan to use it as much as possible, over Ruby/Rails/Sinatra.
Yes. Any business that does more of its work offline than online, is just putting up an online site for convenience.
To answer your question you need consider the following:
1. Ease of use can be more important that exquisite design - Average person does not value design as much as other things such as ease of use.
$0 site that is easy to build/update and done in hours/days > $$$ for beautifully designed by some flaky web designer/developer that takes 4 months to go live
2. Weebly's Design isn't that bad considering how flexible and forgiving the product has to be.
3. Please show me an example of a comparable product to Weebly that is as easy to use and get live but is significantly better designed?
If such a product exists then the answer might be marketing. Rob Walling of Startups for the Rest of Us Market > Marketing > Design > Product (functionality)
It's sad as a developer to see that Design and Functionality come after market/marketing. It also seems to contradict a bit of my point about ease of use for non techies being a reason for Weebly's success, but if they market well, and it's free then they have a huge leg up.
Really considering what it is Weebly aint too shabby. It's also amazing how many crappy sites there are out there that people continue to utilize. I did some cold calls for my startup idea and I thought the people with crappy sites would certainly get on board, but it didn't quite work out that way.
Most aren't "in love" with the program, but they found it easy to get their website put together and running, and figure that if they're looking for their next step they'll just hire someone to build it.
The line I get from most people are along the lines of "it was just... easy... and it worked..."
On those terms, Weebly is quite exemplary.
If it's a shared folder then at some point you explicitly created a link to share access to that folder. If you don't want this anymore, you can revoke access. There is a big link icon next to folders you have shared.
1) https://www.dropbox.com/help/167/en2) https://www.dropbox.com/help/20/en
I always wondered about this as well. Surely if you share the URL with someone, they could reshare it and as you say you then don't know who has access.
Sure, it would be better if it just showed "f_name l_name" instead of email, but I don't think this is a terribly egregious offense. Maybe that's just me though.
Of course if the tech stack kept changing it would be frustrating for the designers to have to junk their designs on a regular basis. But if you have spent a day with them, then you'll be able to make that argument in their language. This will allow you to empathize with their problems, but will also allow you to get inside their OODA loop  and identify things that they may be taking for granted or gaps in their comprehension that are biasing their decisions.
You don't need to be in an adversarial relationship with them, but the weakness in their design process is coming at a cost in engineering resources which they clearly aren't including in their calculations. You can point this out in a non-confrontational way by explaining the time cost of your lost work, and reminding them that 'a stitch in time saves nine.' It's not like you can pass the buck onto Apple or your framework supplier every time the spec changes, any more than the designers have the option of pretending the screen has a different aspect ratio or whatever.
1. OODA is short for Observation-Orientation-Decision-Action, and the 'loop' is the dynamic application of this process in a fluid situation - originally, in military combat. http://en.wikipedia.org/wiki/OODA_loop
I make a list of the type of company I want to work with (I want to be paid $X, they should use this technology, I want to solve this problem or work on this project) and then I backtrace it and figure out which companies match those criteria.
Then, I contact those companies. I set up meetings when I can. My goal is to learn:
* What sort of projects they work on * What challenges they're facing (geez, our biggest client needs _IDEA Z_) * What skills they look for in new hires / freelancers * Other companies in the area / tech / market
Then, I do two things
If they mentioned a huuuuge problem / pain point they're facing, I send them a follow-up email talking about the problem they mentioned, what I can contribute to solving it, and suggesting a time for another meeting.
I follow up with any other companies / people they mentioned and set up a quick coffee meeting.
Periodically, I'll check in with my contact. Nothing spammy, just an update about something relevant to their industry / problem.
Rather than fight over the same jobs that everyone else sees on 37Signals / Reddit / GitHub / HN hiring / Craigslist / LinkedIn / Etc, I want to be at the top of mind with the companies I want to work with.
Every job I've had â€" salary or consulting - has come from someone inside of the company calling me up, telling me about a position they have, and asking me if I want to interview. This bypasses the slog through submitting a resume and fighting against 20+ other candidates for a position. This gets me the positions I want working on the problems I want to solve.
Chasing listed jobs is a mug's game for two reasons: (i) you need to compete with a mountain of applications, and (ii) people often list jobs that they aren't entirely serious about filling. Even if you have a strong resume and put 30 minutes into writing a good cover letter for each applications, the odds really are against you in this case.
Factor (ii) is still a problem if you get an interview because many organizations put multiple random barriers ahead of applicants. For instance, if you don't pass some test or flub a question or one of the fifteen people who talk to you just doesn't like you on an animal level you've wasted all the time you've put into the process.
Anybody who's using a recruiter, on the other hand, really wants to fill the position. The odds are in your favor because the recruiter is going to walk if the company keeps putting candidates through the gauntlet and rejecting them.
So how do you get people to call you?
Be active on the web. For me that's meant developing a few side projects and also developing connections and adding some content to LinkedIn every day... Even when I'm not looking for work.
If you get yourself known you can quit wasting time looking at job boards.
To grow your professional network I would recommend to attend to meetups, hackathons, user groups or even better to get involve in the organization. It worked pretty well for me.
I met some incredible people and got some good jobs offer.
I like that they have to disclose ballpark salaries. Makes it easier to get a sense for how the company values developers.
My previous position was via a university career fair when I was still a student.
(Sadly, the same trick doesn't work for boyfriends.)
This meant that my list of places to apply to actually grew every time I went to go and knock a few off my list. I met a lot of interesting engineers this way and generated a lot of leads that I wouldn't have found through HN Hiring or other boards. In some cases I found jobs that weren't posted online until after I found out about them in person.
go to offline networking events.
get to know your local group for whatever you program in. Seattle-python-interest-group has periodic job emails, and more importantly if I asked them for help I would probably get a couple responses.
I don't look. When I want a new job, I stop ignoring recruiters and wait to see what comes along. I've never waited more than a few days to have a pile of interesting opportunities. (I also end up with a much bigger pile of bullshit talent-trawls, but that's beside the point)
I wish I could say this was a function of my being awesome, but I think it has more to do with the job market in my area (PDX). There just aren't enough senior developers to go around.
- careers.stackoverflow.com - prospects.ac.uk (Though you need to have been a student to register) - s1jobs.com (Mostly so I could have at least seen one ad a day) - talentscotland.com - workinstartups.com
I'm a freelancer, and most of my work comes via referrals now. Not always, but it's been the case for the past few years.
Wasn't much different back when I was looking for full time work though. Even though I only worked for 2 companies, I use to get interviews through referrals, or through past colleagues that left and wanted me to come aboard.
Find the type of company you want to work for. Narrow your list down to about 5 of those companies you'd like to work at.
Now sit down and write a personalized cover letter for each of these companies and the role you'd like to play in said organization.
Now email each of the companies hiring depts, founders, etc with said letter and sit back. If you wrote a truly compelling cover letter (you should have if you are actually passionate about working for the company) you will most likely get some sort of response.
Rinse and repeat if no success.
As a multi-time founder and hiring decision-maker I always enjoyed a good cover letter and great interview more than a resume. Even when it comes to technical knowledge the most important thing to me is that if you did not know it you were smart enough and capable of learning it.
If you can knock it out of the park on a cover letter and show why you're excited to be a part of said company then they would be foolish not to hire you.
EDIT: Obviously you should still send a resume as well. But sending one without a cover letter in my opinion is the equivalent of career suicide.
Get involved: speak at user groups and conferences. If possible, step up and manage. You'll get work sent your way, and once you've built up a reputation (like when people come up to you at conferences and know your name but you don't know theirs), you can often drop the idea of needing work on Twitter and get a good response.
It links to a bunch of job sites. No referral links or anything.
The best part is that it also shows jobs that haven't made it to formal listings yet.
It's at http://www.jobquacks.com - regrettably I haven't built in support for mobile yet..
I'm a UI designer
A Retina laptop might be pretty annoying if you plan on running Windows on it. As Windows gives you literal resolution rather than converting it into a DPI increase (i.e. Windows makes everything REALLY tiny).
EDIT: For me, the 13" Retina MBP does nothing that I wish I could accomplish with my 2011 13" MBP with 8 gigs of RAM and an SSD. It doesn't make anything that I currently do faster/easier/better. Therefore, not much incremental value to me. When I look to buy my next laptop, the Retina series (if its still a different product line by then) will be at the top of my list. I'd love to buy a laptop with an SSD, RAM and that wonderful screen - they just don't provide enough value to overcome the acquisition cost for me.
TLDR; Going from a spinning HD to SSD is worth it. Once you have the screen you will wonder how you dealt without it, but I still wouldn't pay that premium out of my own pocket.
Perhaps you should create some competition? I'll lend a hand... ;)
Without sounding snarky what would you consider their last big mistake?
I would be surprised if they sold a ton of these. Why would I buy a mini over a regular iPad?