lauchmelder/vim-sussify
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

Fortune: use ' instead of `

Browse source 
Keep the fortune file ASCII-clean, according to:

http://english.stackexchange.com/questions/163480/which-is-the-correct-apostrophe-to-use-when-typing-quote-or-backtick
This commit is contained in:
Marco Hinz 2016-03-15 01:42:53 +01:00
parent 0a9e3de72c
commit 6509329585
1 changed files with 37 additions and 37 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

74
autoload/startify/fortune.vim
View file

@ -14,7 +14,7 @@ let s:quotes = exists('g:startify_custom_header_quotes')
\ ['I think a lot of new programmers like to use advanced data structures and advanced language features as a way of demonstrating their ability. I call it the lion-tamer syndrome. Such demonstrations are impressive, but unless they actually translate into real wins for the project, avoid them.', '', '- Glyn Williams'],
\ ['I would rather die of passion than of boredom.', '', '- Vincent Van Gogh'],
\ ['If a system is to serve the creative spirit, it must be entirely comprehensible to a single individual.'],
\ ['The computing scientist`s main challenge is not to get confused by the complexities of his own making.', '', '- E. W. Dijkstra'],
\ ["The computing scientist's main challenge is not to get confused by the complexities of his own making.", '', '- E. W. Dijkstra'],
\ ["Progress in a fixed context is almost always a form of optimization. Creative acts generally don't stay in the context that they are in.", '', '- Alan Kay'],
\ ['The essence of XML is this: the problem it solves is not hard, and it does not solve the problem well.', '', '- Phil Wadler'],
\ ['A good programmer is someone who always looks both ways before crossing a one-way street.', '', '- Doug Linder'],
@ -40,70 +40,70 @@ let s:quotes = exists('g:startify_custom_header_quotes')
\ ['Methods are just functions with a special first argument.', '', '- Andrew Gerrand'],
\
\ ['Care about your craft.', '', 'Why spend your life developing software unless you care about doing it well?'],
\ ['Provide options, don`t make lame excuses.', '', 'Instead of excuses, provide options. Don`t say it can`t be done; explain what can be done.'],
\ ['Be a catalyst for change.', '', 'You can`t force change on people. Instead, show them how the future might be and help them participate in creating it.'],
\ ['Make quality a requirements issue.', '', 'Involve your users in determining the project`s real quality requirements.'],
\ ['Critically analyze what you read and hear.', '', 'Don`t be swayed by vendors, media hype, or dogma. Analyze information in terms of you and your project.'],
\ ['DRY - Don`t Repeat Yourself.', '', 'Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.'],
\ ["Provide options, don't make lame excuses.", '', "Instead of excuses, provide options. Don't say it can't be done; explain what can be done."],
\ ['Be a catalyst for change.', '', "You can't force change on people. Instead, show them how the future might be and help them participate in creating it."],
\ ['Make quality a requirements issue.', '', "Involve your users in determining the project's real quality requirements."],
\ ['Critically analyze what you read and hear.', '', "Don't be swayed by vendors, media hype, or dogma. Analyze information in terms of you and your project."],
\ ["DRY - Don't Repeat Yourself.", '', 'Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.'],
\ ['Eliminate effects between unrelated things.', '', 'Design components that are self-contained, independent, and have a single, well-defined purpose.'],
\ ['Use tracer bullets to find the target.', '', 'Tracer bullets let you home in on your target by trying things and seeing how close they land.'],
\ ['Program close to the problem domain.', '', 'Design and code in your user`s language.'],
\ ['Program close to the problem domain.', '', "Design and code in your user's language."],
\ ['Iterate the schedule with the code.', '', 'Use experience you gain as you implement to refine the project time scales.'],
\ ['Use the power of command shells.', '', 'Use the shell when graphical user interfaces don`t cut it.'],
\ ['Use the power of command shells.', '', "Use the shell when graphical user interfaces don't cut it."],
\ ['Always use source code control.', '', 'Source code control is a time machine for your work - you can go back.'],
\ ['Don`t panic when debugging', '', 'Take a deep breath and THINK! about what could be causing the bug.'],
\ ['Don`t assume it - prove it.', '', 'Prove your assumptions in the actual environment - with real data and boundary conditions.'],
\ ["Don't panic when debugging", '', 'Take a deep breath and THINK! about what could be causing the bug.'],
\ ["Don't assume it - prove it.", '', 'Prove your assumptions in the actual environment - with real data and boundary conditions.'],
\ ['Write code that writes code.', '', 'Code generators increase your productivity and help avoid duplication.'],
\ ['Design With contracts.', '', 'Use contracts to document and verify that code does no more and no less than it claims to do.'],
\ ['Use assertions to prevent the impossible.', '', 'Assertions validate your assumptions. Use them to protect your code from an uncertain world.'],
\ ['Finish what you start.', '', 'Where possible, the routine or object that allocates a resource should be responsible for deallocating it.'],
\ ['Configure, don`t integrate.', '', 'Implement technology choices for an application as configuration options, not through integration or engineering.'],
\ ['Analyze workflow to improve concurrency.', '', 'Exploit concurrency in your user`s workflow.'],
\ ['Always design for concurrency.', '', 'Allow for concurrency, and you`ll design cleaner interfaces with fewer assumptions.'],
\ ["Configure, don't integrate.", '', 'Implement technology choices for an application as configuration options, not through integration or engineering.'],
\ ['Analyze workflow to improve concurrency.', '', "Exploit concurrency in your user's workflow."],
\ ['Always design for concurrency.', '', "Allow for concurrency, and you'll design cleaner interfaces with fewer assumptions."],
\ ['Use blackboards to coordinate workflow.', '', 'Use blackboards to coordinate disparate facts and agents, while maintaining independence and isolation among participants.'],
\ ['Estimate the order of your algorithms.', '', 'Get a feel for how long things are likely to take before you write code.'],
\ ['Refactor early, refactor often.', '', 'Just as you might weed and rearrange a garden, rewrite, rework, and re-architect code when it needs it. Fix the root of the problem.'],
\ ['Test your software, or your users will.', '', 'Test ruthlessly. Don`t make your users find bugs for you.'],
\ ['Don`t gather requirements - dig for them.', '', 'Requirements rarely lie on the surface. They`re buried deep beneath layers of assumptions, misconceptions, and politics.'],
\ ['Test your software, or your users will.', '', "Test ruthlessly. Don't make your users find bugs for you."],
\ ["Don't gather requirements - dig for them.", '', "Requirements rarely lie on the surface. They're buried deep beneath layers of assumptions, misconceptions, and politics."],
\ ['Abstractions live longer than details.', '', 'Invest in the abstraction, not the implementation. Abstractions can survive the barrage of changes from different implementations and new technologies.'],
\ ['Don`t think outside the box - find the box.', '', 'When faced with an impossible problem, identify the real constraints. Ask yourself: "Does it have to be done this way? Does it have to be done at all?"'],
\ ['Some things are better done than described.', '', 'Don`t fall into the specification spiral - at some point you need to start coding.'],
\ ['Costly tools don`t produce better designs.', '', 'Beware of vendor hype, industry dogma, and the aura of the price tag. Judge tools on their merits.'],
\ ['Don`t use manual procedures.', '', 'A shell script or batch file will execute the same instructions, in the same order, time after time.'],
\ ["Don't think outside the box - find the box.", '', 'When faced with an impossible problem, identify the real constraints. Ask yourself: "Does it have to be done this way? Does it have to be done at all?"'],
\ ['Some things are better done than described.', '', "Don't fall into the specification spiral - at some point you need to start coding."],
\ ["Costly tools don't produce better designs.", '', 'Beware of vendor hype, industry dogma, and the aura of the price tag. Judge tools on their merits.'],
\ ["Don't use manual procedures.", '', 'A shell script or batch file will execute the same instructions, in the same order, time after time.'],
\ ["Coding ain't done 'til all the Tests run.", '', "'Nuff said."],
\ ['Test state coverage, not code coverage.', '', 'Identify and test significant program states. Just testing lines of code isn`t enough.'],
\ ['Test state coverage, not code coverage.', '', "Identify and test significant program states. Just testing lines of code isn't enough."],
\ ['English is just a programming language.', '', 'Write documents as you would write code: honor the DRY principle, use metadata, MVC, automatic generation, and so on.'],
\ ['Gently exceed your users` expectations.', '', 'Come to understand your users` expectations, then deliver just that little bit more.'],
\ ["Gently exceed your users' expectations.", '', "Come to understand your users' expectations, then deliver just that little bit more."],
\ ['Think about your work.', '', 'Turn off the autopilot and take control. Constantly critique and appraise your work.'],
\ ['Don`t live with broken windows.', '', 'Fix bad designs, wrong decisions, and poor code when you see them.'],
\ ['Remember the big picture.', '', 'Don`t get so engrossed in the details that you forget to check what`s happening around you.'],
\ ["Don't live with broken windows.", '', 'Fix bad designs, wrong decisions, and poor code when you see them.'],
\ ['Remember the big picture.', '', "Don't get so engrossed in the details that you forget to check what's happening around you."],
\ ['Invest regularly in your knowledge portfolio.', '', 'Make learning a habit.'],
\ ['It`s both what you say and the way you say it.', '', 'There`s no point in having great ideas if you don`t communicate them effectively.'],
\ ['Make it easy to reuse.', '', 'If it`s easy to reuse, people will. Create an environment that supports reuse.'],
\ ["It's both what you say and the way you say it.", '', "There's no point in having great ideas if you don't communicate them effectively."],
\ ['Make it easy to reuse.', '', "If it's easy to reuse, people will. Create an environment that supports reuse."],
\ ['There are no final decisions.', '', 'No decision is cast in stone. Instead, consider each as being written in the sand at the beach, and plan for change.'],
\ ['Prototype to learn.', '', 'Prototyping is a learning experience. Its value lies not in the code you produce, but in the lessons you learn.'],
\ ['Estimate to avoid surprises.', '', 'Estimate before you start. You`ll spot potential problems up front.'],
\ ['Keep knowledge in plain text.', '', 'Plain text won`t become obsolete. It helps leverage your work and simplifies debugging and testing.'],
\ ['Estimate to avoid surprises.', '', "Estimate before you start. You'll spot potential problems up front."],
\ ['Keep knowledge in plain text.', '', "Plain text won't become obsolete. It helps leverage your work and simplifies debugging and testing."],
\ ['Use a single editor well.', '', 'The editor should be an extension of your hand; make sure your editor is configurable, extensible, and programmable.'],
\ ['Fix the problem, not the blame.', '', 'It doesn`t really matter whether the bug is your fault or someone else`s - it is still your problem, and it still needs to be fixed.'],
\ ['"select" isn`t broken.', '', 'It is rare to find a bug in the OS or the compiler, or even a third-party product or library. The bug is most likely in the application.'],
\ ['Fix the problem, not the blame.', '', "It doesn't really matter whether the bug is your fault or someone else's - it is still your problem, and it still needs to be fixed."],
\ ["\"select\" isn't broken.", '', 'It is rare to find a bug in the OS or the compiler, or even a third-party product or library. The bug is most likely in the application.'],
\ ['Learn a text manipulation language.', '', 'You spend a large part of each day working with text. Why not have the computer do some of it for you?'],
\ ['You can`t write perfect software.', '', 'Software can`t be perfect. Protect your code and users from the inevitable errors.'],
\ ["You can't write perfect software.", '', "Software can't be perfect. Protect your code and users from the inevitable errors."],
\ ['Crash early.', '', 'A dead program normally does a lot less damage than a crippled one.'],
\ ['Use exceptions for exceptional problems.', '', 'Exceptions can suffer from all the readability and maintainability problems of classic spaghetti code. Reserve exceptions for exceptional things.'],
\ ['Minimize coupling between modules.', '', 'Avoid coupling by writing "shy" code and applying the Law of Demeter.'],
\ ['Put abstractions in code, details in metadata.', '', 'Program for the general case, and put the specifics outside the compiled code base.'],
\ ['Design using services.', '', 'Design in terms of services-independent, concurrent objects behind well-defined, consistent interfaces.'],
\ ['Separate vIews from models.', '', 'Gain flexibility at low cost by designing your application in terms of models and views.'],
\ ['Don`t program by coincidence.', '', 'Rely only on reliable things. Beware of accidental complexity, and don`t confuse a happy coincidence with a purposeful plan.'],
\ ['Test your estimates.', '', 'Mathematical analysis of algorithms doesn`t tell you everything. Try timing your code in its target environment.'],
\ ["Don't program by coincidence.", '', "Rely only on reliable things. Beware of accidental complexity, and don't confuse a happy coincidence with a purposeful plan."],
\ ['Test your estimates.', '', "Mathematical analysis of algorithms doesn't tell you everything. Try timing your code in its target environment."],
\ ['Design to test.', '', 'Start thinking about testing before you write a line of code.'],
\ ['Don`t use wizard code you don`t understand.', '', 'Wizards can generate reams of code. Make sure you understand all of it before you incorporate it into your project.'],
\ ['Work with a user to think like a user.', '', 'It`s the best way to gain insight into how the system will really be used.'],
\ ["Don't use wizard code you don't understand.", '', 'Wizards can generate reams of code. Make sure you understand all of it before you incorporate it into your project.'],
\ ['Work with a user to think like a user.', '', "It's the best way to gain insight into how the system will really be used."],
\ ['Use a project glossary.', '', 'Create and maintain a single source of all the specific terms and vocabulary for a project.'],
\ ['Start when you`re ready.', '', 'You`ve been building experience all your life. Don`t ignore niggling doubts.'],
\ ['Don`t be a slave to formal methods.', '', 'Don`t blindly adopt any technique without putting it into the context of your development practices and capabilities.'],
\ ['Organize teams around functionality.', '', 'Don`t separate designers from coders, testers from data modelers. Build teams the way you build code.'],
\ ["Start when you're ready.", '', "You've been building experience all your life. Don't ignore niggling doubts."],
\ ["Don't be a slave to formal methods.", '', "Don't blindly adopt any technique without putting it into the context of your development practices and capabilities."],
\ ['Organize teams around functionality.', '', "Don't separate designers from coders, testers from data modelers. Build teams the way you build code."],
\ ['Test early. Test often. Test automatically.', '', 'Tests that run with every build are much more effective than test plans that sit on a shelf.'],
\ ['Use saboteurs to test your testing.', '', 'Introduce bugs on purpose in a separate copy of the source to verify that testing will catch them.'],
\ ['Find bugs once.', '', 'Once a human tester finds a bug, it should be the last time a human tester finds that bug. Automatic tests should check for it from then on.'],