Joel Spolskys Concise Guide to Finding the Best Technical Talent Pdf, Epub, Ebook
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!) - Joel on Software
The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!) - Joel on Software Joel on Software The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!) by Joel Spolsky Wednesday, October 08, 2003 Ever wonder about that mysterious Content-Type tag? You know, the one you're supposed to put in HTML and you never quite know what it should be? Did you ever get an email from your friends in Bulgaria with the subject line "???? ?????? ??? ????"? I've been dismayed to discover just how many software developers aren't really completely up to speed on the mysterious world of character sets, encodings, Unicode, all that stuff. A couple of years ago, a beta tester for FogBUGZ was wondering whether it could handle incoming email in Japanese. Japanese? They have email in Japanese? I had no idea. When I looked closely at the commercial ActiveX control we were using to parse MIME email messages, we discovered it was doing exactly the wrong thing with character sets, so we actually had to write heroic code to undo the wrong conversion it had done and redo it correctly. When I looked into another commercial library, it, too, had a completely broken character code implementation. I corresponded with the http://www.joelonsoftware.com/articles/Unicode.html[5/11/2014 1:30:52 AM] The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!) - Joel on Software developer of that package and he sort of thought they "couldn't do anything about it." Like many programmers, he just wished it would all blow over somehow. -
Finding a Growth Business Model at Stackoverflow-Final2
S TANFORD U NIVERSITY 2 0 1 0 - 2 0 4 - 1 S CHOOL OF E NGINEERING C ASEP UBLISHER Rev. July 20, 2010 CITE AS: M. Sewak et al. “Finding a Growth Business Model at Stack Overflow, Inc.” Stanford CasePublisher 204-2010-1. 18 May 2010. FINDING A GROWTH BUSINESS MODEL AT STACK OVERFLOW, INC. T ABLE OF C ONTENTS Introduction 1. The Founders 1.1. Joel Spolsky 1.2. Jeff Atwood 2. History of Online Q&A Sites 3. History of Stack Overflow 3.1. Metrics 3.2. Market Reaction 4. Revenue Models 5. Overall Market 6. User Growth Models for Stack Overflow 6.1. Hosted Whitelabel 6.2. Network of Experts 6.3. Monolithic Site 7. Recent Financing Activity 8. The Future 9. Discussion Questions 10. Exhibits 11. References Professors Micah Siegel (Stanford University) and Fred Gibbons (Stanford University) guided the de- velopment of this case using the CasePublisher service as the basis for class discussion rather than to il- lustrate either effective or ineffective handling of a business situation. S TANFORD 204-2010-01 Finding Business Model at Stack Overflow Introduction ! Joel Spolsky and Je" Atwood had launched Stack Overflow less than two years ago, and it had already crossed the 175,000 mark in terms of registered users. The creation of an open platform where programming questions were promptly answered was an achievement in itself. However, Spolsky and Atwood faced their next challenge: coming up with a revenue model to monetize the popularity of Stack Overflow. Led by their frustration with other programming related Q&A websites, Spolsky and At- wood had started Stack Overflow to enable users to find answers to programming questions. -
Finding High–Quality Grey Literature for Use As Evidence in Software Engineering Research
Finding high{quality grey literature for use as evidence in software engineering research A thesis submitted in partial fulfilment of the requirements for the Degree of Doctor of Philosophy in the University of Canterbury by Ashley Williams University of Canterbury 2019 To my Grandad, Norman For encouraging me to push myself; and ensuring that I never miss a family Christmas Abstract Background: Software engineering research often uses practitioners as a source of evidence in their studies. This evidence is usually gathered through empirical methods such as surveys, interviews and ethnographic research. The web has brought with it the emergence of the social programmer. Soft- ware practitioners are publishing their opinions online through blog articles, discussion boards and Q&A sites. Mining these online sources of informa- tion could provide a new source of evidence which complements traditional evidence sources. There are benefits to the adoption of grey literature in software engi- neering research (such as bridging the gap between the state{of{art where research typically operates and the state{of{practice), but also significant challenges. The main challenge is finding grey literature which is of high{ quality to the researcher given the vast volume of grey literature available on the web. The thesis defines the quality of grey literature in terms of its relevance to the research being undertaken and its credibility. The thesis also focuses on a particular type of grey literature that has been written by soft- ware practitioners. A typical example of such grey literature is blog articles, which are specifically used as examples throughout the thesis. -
The Joel Test: 12 Steps to Better Code
AUGUST 9, 2000 by JOEL SPOLSKY The Joel Test: 12 Steps to Better Code TOP 10, ROCK STAR DEVELOPER, NEWS Have you ever heard of SEMA? It’s a fairly esoteric system for measuring how good a so!ware team is. No, wait! Don’t follow that link! It will take you about six years just to understand that stu". So I’ve come up with my own, highly irresponsible, sloppy test to rate the quality of a so!ware team. The great part about it is that it takes about 3 minutes. With all the time you save, you can go to medical school. The Joel Test 1. Do you use source control? 2. Can you make a build in one step? 3. Do you make daily builds? 4. Do you have a bug database? 5. Do you fix bugs before writing new code? 6. Do you have an up-to-date schedule? 6. Do you have an up-to-date schedule? 7. Do you have a spec? 8. Do programmers have quiet working conditions? 9. Do you use the best tools money can buy? 10. Do you have testers? 11. Do new candidates write code during their interview? 12. Do you do hallway usability testing? The neat thing about The Joel Test is that it’s easy to get a quick yes or no to each question. You don’t have to figure out lines-of-code-per-day or average-bugs- per-inflection-point. Give your team 1 point for each “yes” answer. The bummer about The Joel Test is that you really shouldn’t use it to make sure that your nuclear power plant so!ware is safe. -
Ebook Download Smart and Gets Things Done: Joel Spolskys
SMART AND GETS THINGS DONE: JOEL SPOLSKYS CONCISE GUIDE TO FINDING THE BEST TECHNICAL TALENT PDF, EPUB, EBOOK Avram Joel Spolsky | 218 pages | 01 Jun 2007 | aPress | 9781590598382 | English | New York, United States Smart and Gets Things Done: Joel Spolskys Concise Guide to Finding the Best Technical Talent PDF Book I had the same problem today, and learned a lot. It seems that you're in Germany. Interesting perspective on what you should look for when hiring for tech. Joel not only understands it, he also bases his company on the idea and provides some rather convincing data and discussions. How to find people who are not on the market: 1. Published May 1st by Apress first published January 1st It's an interesting and important introductory chapter that sets the stage for the rest of the book. American, New Zealand , Israeli, Dual citizenship [1]. The Identity Method Make people identify with the goals you're trying to achieve The Identity Method is a way to create intrinsic motivation. The advice is all fairly solid, the issue being that it's solid for a company that is able to pay well and give top software engineers what they want. Solid short read. His personal website, Joel on Software, has been popular with developers around the world since its inception in and has been translated into over 30 languages. In that time, she has built highly-productive and successful teams to deliver high quality software efficiently, and established delivery processes to achieve growth. He is the author of Joel on Software , a blog on software development, and the creator of the project management software Trello.