background preloader

Culture

Facebook Twitter

Everything Wraxnia! Lexicography. Future - The ‘untranslatable’ emotions you never knew you had. This story is featured in BBC Future’s “Best of 2017” collection. Discover more of our picks. Have you ever felt a little mbuki-mvuki – the irresistible urge to “shuck off your clothes as you dance”? Perhaps a little kilig – the jittery fluttering feeling as you talk to someone you fancy?

How about uitwaaien – which encapsulates the revitalising effects of taking a walk in the wind? These words – taken from Bantu, Tagalog, and Dutch – have no direct English equivalent, but they represent very precise emotional experiences that are neglected in our language. And if Tim Lomas at the University of East London has his way, they might soon become much more familiar. Lomas’s Positive Lexicography Project aims to capture the many flavours of good feelings (some of which are distinctly bittersweet) found across the world, in the hope that we might start to incorporate them all into our daily lives. Welcome to The Human Planet. Unsettling Stories | Short horror stories by Max Lobdell. What are Air Plants? — Hemleva. Allow them to dry completely before placing them back into their home, to avoid mold. They should not be placed in soil, and they love bright, indirect sunlight, or artificial light, and require good air circulation. ▲ L O O K F O R ▲A good tell for whether or not they are thirsty is the curvature of the leaves of your Air Plant.

They will curl in as they are getting a little too dry. Their roots are only there for anchoring them as they grow, but are not necessary to maintain, and can be trimmed down without harm to the plant. If the tips begin to dry out, it is a sign that they might be getting too much direct sunlight or are a little dry. You can also clip the dry tips with clean scissors. You should then remedy the care by moving it out of direct sunlight or increase your watering or misting. ▲ Q U E S T I O N S ? Seeing Ear Theatre. Back in 2003, for our features page, I wrote the following about Seeing Ear Theatre: In the United States, radio drama is virtually dead. But just after the internet blossomed, “radio” drama briefly revived itself. Between 1997 and 2001 dozens of Science Fiction and Fantasy stories were produced by a dedicated and talented crew of multimedia artists, writers, actors and musicians using the RealPlayer technology to delivery “radio” drama via streaming audio.

And what a revival it was! Starting small and building bigger and better productions until its demise, the SEEING EAR THEATRE was arguably much better than the SCI-FI channel that spawned it. It managed to capture some of the top living SF writers of today, like Harlan Ellision, J. Michael Straczynski, and Kim Stanley Robinson. Much of Seeing Ear Theatre‘s output was, until 2007, available at the abandoned SET section of the Sci-Fi Channel’s website. Until now. Enjoy! Seeing Ear Theatre – Kindred Based on the novel by Octavia E. By J. Welcome to Forbes. Marauders Map. Happy Japanese Emoticons | Kaomoji, Emoji & Dongers. Happy kaomojis are probably the most common of all Japanese emoticons and that’s probably why this category is the largest one on the site.

All of these Japanese emoticons are happy with happy smiling mouths or happy cute eyes full of joy and mirth. For happy looking emoticons you usually want to use eyes that are high up. The best characters to use for these are ^, ´, `, or ⌒ among others. The best characters to use for mouths are ones like ▽, ∀ or ω if you want to be cute. You can also add * or # for rosey cheeks or add waving arms with things like , /, ヽ or ノ. Famous Happy Emoticons Some of the more famous or classic happy looking Japanese emoticons. Triangle Mouths These happy kaomoji emoticons have triangles for mouths.

Upside Down A Mouths These dongers all use an upside down A character (∀) for mouths. Squiggly Mouths These emojis have squiggly happy looking mouths using characters such as ̫ or ~. V Mouths These Japanese emoticons simply use the English letter v for a mouth. Grabby Hands. T E X T F I L E S. The Current File Statistics for textfiles.comCheck the bottom of the main page for related sites, include ANSI, audio, PDF, and others. Do everyone a favor and read the Disclaimer. AAAAH! MY EYES! Click here if you prefer a black and white color scheme. Many people want to download an entire directory and sift through it on their own time.

To assist this research, most of the directories have a file at the end that is an archive of that entire directory. Do you have textfiles you want to donate that are not here? Want to keep employees happy? Give them a quiz - Apr. 22, 2015. The online survey, and its anonymous responses, are reviewed at an all-hands meeting the next week, and the results are graphed over time. "Something that's near and dear to us is transparency," said Craig Cincotta, a spokesperson for Porch, which offers home improvement ideas and professionals who can make those ideas happen. Employee happiness is something Cincotta thinks about every day, and TINYpulse, a survey tool, is helping him track it. Related: Are you depressed? Find out in 90 seconds TINYpulse crowdsources information from employees using one question per week, which can be pulled from the TINYpulse database or written by the company. Something that emerged at Porch was criticism about the open-plan seating.

The company is growing fast, and raised $100 million in its first year. In the beginning, it was easy to get a sense of how engaged and happy people were. "When we got to 150 people, it became harder to get that real-time information on how people were feeling," Cincotta said.

Terraria

Play The Odyssey Compleat Adventure rom Game Online - Apple II free appleii. This Is Probably The Most High-Tech Cemetery In the World. Unsorted Ascii Art. Funnymouth. * funnymouth has joined #ReferSales. funnymouth: hello everyone tonight funnymouth: i like to lik the bluud funnymouth: out of in the person funnymouth: i see ur handsome face dont b so sad about it funnymouth: come on funnymouth: :) * funnymouth has left #ReferSales. GhostJeorge: ... Holy fuck, what the fuck lemonlimeskull: Did that just happen? GhostJeorge: Yes, Skull. Yes it did. The first thing I should probably note is that I'm "lemonlimeskull". That was the first time I saw or heard from "funnymouth", and for all intents and purposes, it should've been the last. What first struck me as odd about the funnymouth guy, however, was the fact that he came and went with no particular GOAL. He just stuck his head in, rattled off some random text, and happily fucked off. lemonlimeskull: So really though, what the Hell?

I don't know what results I expected from following this guy to another channel. I guess what I'm saying is I have no idea why I pursued this. And with that, I left. Nothing. Classic Mistakes Enumerated. Some ineffective development practices have been chosen so often, by so many people, with such predictable, bad results that they deserve to be called "classic mistakes. " Most of the mistakes have a seductive appeal. Do you need to rescue a project that's behind schedule? Add more people! Do you want to reduce your schedule?

Schedule more aggressively! Is one of your key contributors aggravating the rest of the team? Wait until the end of the project to fire him! Developers, managers, and customers usually have good reasons for making the decisions they do, and the seductive appeal of the classic mistakes is part of the reason these mistakes have been made so often. This section enumerates three dozen classic mistakes. The common denominator in this list is that you won't necessarily get rapid development if you avoid the mistake, but you will definitely get slow development if you don't avoid it. If some of these mistakes sound familiar, take heart. People #1: Undermined motivation. Fizz Buzz Test. The "Fizz-Buzz test" is an interview question designed to help filter out the 99.5% of programming job candidates who can't seem to program their way out of a wet paper bag. The text of the programming assignment is as follows: "Write a program that prints the numbers from 1 to 100.

But for multiples of three print “Fizz” instead of the number and for the multiples of five print “Buzz”. For numbers which are multiples of both three and five print “FizzBuzz”. " Source: "Using FizzBuzz to Find Developers who Grok Coding" ''It would be more interesting if the numbers were -50 to +50. -- mt <+*i + 67 Articles: I never got the fizz buzz test, but out of the blue lately I've been asked such stupid questions I was amazed I was even asked.

Why Fizz-Buzz is "hard:" We can't understand why so many people "fail" the Fizz-Buzz test unless we understand why it is "hard" (for them). [ick!!!] -- MarcThibault #! Or. This is why you never end up hiring good developers - Quartz. You are bad at giving technical interviews. Yes, you. You’re looking for the wrong skills, hiring the wrong people, and actively screwing yourself and your company.

Without changing anything about your applicant pool, you can hire different people and your company will do better and you will enjoy your job more. I realize these are bold claims. In the ten years since I became senior enough to be asked to interview people, I have conducted a great number of technical interviews, been part of a lot of teams at companies big and small, and watched the effect that different types of hires have had on those companies. You are looking for the wrong things 1. The primary mistake that people make when interviewing is over-valuing present skills and under-valuing future growth. But even worse is the way we try to determine whether people have these skills. 2.

I used to ask people to write code in interviews. 3. Some people are impressed by academic credentials. 4. 5. Can they do this job? 1. 2. Evidence Based Scheduling. Evidence Based Scheduling by Joel Spolsky Friday, October 26, 2007 Software developers don’t really like to make schedules. Usually, they try to get away without one. “It’ll be done when it’s done!” They say, expecting that such a brave, funny zinger will reduce their boss to a fit of giggles, and in the ensuing joviality, the schedule will be forgotten. Most of the schedules you do see are halfhearted attempts. Hilarious! You want to be spending your time on things that get the most bang for the buck. Why won’t developers make schedules? Over the last year or so at Fog Creek we’ve been developing a system that’s so easy even our grouchiest developers are willing to go along with it.

The steeper the curve, the more confident you are that the ship date is real. Here’s how you do it. 1) Break ‘er down When I see a schedule measured in days, or even weeks, I know it’s not going to work. This forces you to actually figure out what you are going to do. 2) Track elapsed time You can’t, really. Next: Giles Bowkett: Why Scrum Should Basically Just Die In A Fire. Conversations with Panda Strike CEO Dan Yoder inspired this blog post. Consider story points. If you're not familiar with Scrum, here's how they work: you play a game called "Planning Poker," where somebody calls out a task, and then counts down from three to one.

On one, the engineers hold up a card with the number of "story points" which represents the relative cost they estimate for performing the task. So, for example, a project manager might say "integrating our login system with OpenAuth and Bitcoin," and you might put up the number 20, because it's the maximum allowable value. Wikipedia describes the goal of this game: The reason to use Planning Poker is to avoid the influence of the other participants.

I have literally never seen Planning Poker performed in a way which fails to undermine this goal. Wikipedia gives the alleged structure of this process: In fairness to everybody who's tried this process and seen it fail, how could it not devolve? And you never will. Please buy it. Why? Recommended Reading for Developers. Code Complete 2 Steve McConnell's Code Complete 2 is the Joy of Cooking for software developers. Reading it means that you enjoy your work, you're serious about what you do, and you want to keep improving. In Code Complete, Steve notes that the average programmer reads less than one technical book per year. The very act of reading this book already sets you apart from probably ninety percent of your fellow developers. I like this book so much that the title of this very website is derived from it – the examples of what not to do are tagged with the "Coding Horror" icon. The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) Arguably the only classic book in our field.

I challenge any developer to pick up a copy of The Mythical Man Month and not find this tale of a long-defunct OS, and the long-defunct team that developed it, startlingly relevant. Don't Make Me Think: A Common Sense Approach to Web Usability Er… yeah. Rapid Development Why? New Programming Jargon. Stack Overflow – like most online communities I've studied – naturally trends toward increased strictness over time. It's primarily a defense mechanism, an immune system of the sort a child develops after first entering school or daycare and being exposed to the wide, wide world of everyday sneezes and coughs with the occasional meningitis outbreak. It isn't always a pleasant process, but it is, unfortunately, a necessary one if you want to survive. Consider this question from two years ago: New programming jargon you coined?

Is this even a question, really? Three hundred and eighty six! A question that invites 386 different "answers" isn't a question at all. I won't bore you with the entire history, our so-called "war on fun", and the trouble with popularity. In terms of programmer culture, though, there is precedent in the form of The Jargon File. 1. Using if(constant == variable) instead of if(variable == constant), like if(4 == foo). 2. For when you just Gotta Catch 'Em All. 3. 4. 5.

How do I ask a good question? - Help Center. Rubber Duck Problem Solving. At Stack Exchange, we insist that people who ask questions put some effort into their question, and we're kind of jerks about it. That is, when you set out to ask a question, you should … Describe what's happening in sufficient detail that we can follow along. Provide the necessary background for us to understand what's going on, even if we aren't experts in your particular area.Tell us why you need to know the answer. What led you here? Is it idle curiosity or is this somehow blocking you on a project? We don't need your whole life story, just give us some context here.Share your research on your problem; what have you found so far?

Why didn't it work? We have a great How to Ask page that explains all of this, which is linked generously throughout the network. What we're trying to prevent, most of all, is the unanswerable drive-by question. Like I said, we're kinda jerks about this. It's quite common. How can I thank the community when I solve my own problems? Project Euler Solutions. C# Solutions for Project Euler | MathBlog. The Rands Test. Forms in English Haiku - Graceguts. Capital - The victims of open offices are pushing back. 11 Steps Attackers Took to Crack Target | CIO. 10 company name types on TechCrunch: Pros and cons : The Name Inspector. 20 of the Most Painful Lessons IT Pros Had to Learn the Hard Way | CIO. 2048 Infinite - The Circle of Fifths - Learn Music Theory Music Interactive. Binary to Text (ASCII) Conversion. Coding Horror. Programming Sucks. The Elements Edition. Prism. Programming Sucks. The coding love. 6 Books Every Programmer Should Own.

2048 Game - 2048 Colors Mode. 2584 Fibonacci - Play on Crazy Games. The Ultimate Software Development Office Layout. Misc/p339-teasley.pdf. Flag Designer. Online SVG to PNG/JPEG/TIFF conversion. Mythical man month diagram. 'Syndromes' Drive Coders Crazy. Ea_spouse: EA: The Human Story. I Knew a Programmer that Went Completely Insane. Coding Horror. What to Do With a Workplace Whiner. Go the F**k Home. Soda Machine Hack | Skatter Tech. 2048.