636 karma · joined November 29, 2012
The way it would work is that you'd install our plugin onto your site and make all of the images hoverable and linkable. Then, when people purchase through those links, you make an affiliate commission. The way we'd envision it working is that users would get a percent of the commission of whatever purchases they drove, and your site would also get a percent of the commission.
Founder of PLEENQ here. I didn't want to complicate the video, but the quick explanation is this:
1. A user links an item in an image to what it is. That could be an IMDB page, a Wikipedia page, or where to buy the item.
2. Other users click through the link, and if a product, are linked directly to where to purchase the item.
3. If a user purchases the item, the person who created the link gets paid a percentage of the total price of the item (the affiliate commission).
We're currently in public beta, so feel free to download it and try it out. It's a chrome extension right now, but we will expand it to firefox and safari in the future.
Another note: you can inject PLEENQ directly into your web page to give the functionality to the users of your site. We're onboarding over 30 blogs this month that are including this functionality into their site and help their site monetize. Feel free to contact me at justin@pleenq.com if you're interested in that.
Every single year people who are read onto FISA must complete a comprehensive course on how to deal with FISA data, and it's not taken lightly. People lose their job over mishandling of this type of data, for reasons such as: poor query construction, failure to timely delete accidental collection on US Persons, or collecting without prior justification.
The whole point is to get someone from knowing nothing about electronics to being able to troubleshoot a system down to an offending circuit card, and replace the part. There are more advanced schools, such as the journeyman technician school, which works on breaking down some of the wrong information they might have picked up on over the course of applying these practical concepts, and building up enough knowledge to troubleshoot down to the component-level. That course will get them through things like back-plane wiring, ohm'ing out bad pins on cables that run through the ship (and therefore are impossible to easily touch end-to-end), and sometimes even gets to desoldering individual components on cards and replacing them, in order to save on paying Raytheon $4000 for a card that cost them $1.50 to make.
With that in mind, almost no one that goes through these courses actually goes on to become an engineer, or really strives to understand the true nature of the forces that make their systems possible. For the most part, you can take these students and give them a broken system with hot-swappable components and the schematics for it, and they could fix it. To me, that's the true measure of success of these books.
A few weeks ago, my startup[1] did a crunch mode week before releasing our beta to the first set of users. We had promised access to the application on a certain day, and I am absolutely never going to be convinced that missing a deadline that you've promised someone else is an okay thing to do, as the article suggests as a form of self-punishment. In doing so, I did a few things in order to take care of my one employee. First, I said that lunch and dinner would be covered by the company, since we were both staying there until the nighttime hours. Second, I made a Costco run and got us anything would could need to snack on or drink during the week (not very expensive when you're buying for two people). Third, immediately following our successful launch on a Monday, he had Tuesday and Friday off. It's very important that when you're not on crunch that it feels like you're not on crunch, and you "make up" for the time that you burned through.
I am always of the opinion that if you're not willing to put in a ton of hours, there's someone just as smart and focused as you that is. I think my perspective has been forever changed, though, because I've been on deployments where we worked 12 hours a day for 9 months straight with no holidays, doing knowledge work I might add. Becoming accustomed to that makes everything that comes after it seem incredibly easy.
Both my employee and I feel incredibly lucky to be working on something that we both really believe has a chance to succeed greatly, and it is so much a part of our lives that when we're not at work we're thinking of more ways we can improve our product. When you're that deep into an idea, be it a business, hobby, love interest, etc., the amount of time you spend on it always seems like not enough. I think people bristling about long work hours are doing so because they haven't found something that makes them feel this way.
Some thoughts:
-I'd like to be able to edit my profile
-As you know, having the search feature will be an important addition
-Can't collapse comment threads. I'd like a button in the whitespace on the same line as the commenter that I could click to collapse.
-Saving draft comments would be helpful. When I was typing this I had to select all -> copy and go back to another screen to check something, then paste it back in. Some type of way of marking drafts directly in the thread would be cool. I think it would have the advent of allowing me to start a draft in a comment thread that I was interested in replying to later, and then be able to return to it when I had more time. This would be coupled with listing out "drafts" in the sections up top.
-Special coloring for the original posters posting in the comment threads. At least for the names, if not changing the background color of the comment a shade or two.
-This one is not as feasible, but saving versions of comments when I've come back to the same thread. I'd like a diff on comments in case someone edits something, so I can replay it back to the original comments I saw. Maybe only saving the histories for the last 100 threads, since if I'm returning to a thread it wouldn't be 100 thread views later.
I was an Arabic linguist at the NSA, and would input certain numbers I'd hear into a tool. Whenever I heard a specific one, I was supposed to add 9 to it and put that number into the tool. This drove me insane, because I kept asking why I had to add 9 myself, instead of the program just doing it (since I could describe the rule myself). I started putting in trouble tickets every few months, but they were all ignored. At one point, I just decided I was going to fix it myself, and approached the guy who made the tool and asked him for permission to modify the program to fix it. He handed me the O'Reilly Perl Cookbook, and said to go to town on it.
I ended up finding out in the code how to fix the problem within the first day, and started thinking about other ways I could improve the program to make our lives easier. I made all sorts of improvements, and my cubicle neighbors saw this and asked if there was any way I could make a tool for simplifying their manual process. I got to work on it, and quickly whipped out something that stored all of their entries for later review. The big problem at the time was that I didn't have any basic knowledge of CS -- I didn't even know what a database was, so I built a system of just storing all of the text in flatfiles and using Perl's Tie::File to turn the files into dynamic arrays.
I started making program after program, and what drew me to my career was walking by someone's computer and seeing the program I built on their desktops as they were working. Eventually, the entire division of 80-90 people were all using my programs for their day-to-day, and I had to quickly learn a lot of hard lessons about putting things into production.
So, in short, I think the big reason I chose my current career was that I always loved building things that people not only wanted to use, but thanked me for building them because of how much easier it made their lives. There is nothing more satisfying (to me) than building something useful and having people who use it think you're a modern day magician.
The eventual website will be more of a web application akin to twitter, instead of a signup landing page. We've just prioritized releasing the actual extension ahead of getting the website done, since the probability of an organic signup was next to nothing.
As you said, though, it turns out it was just much easier to bootstrap the entire thing since it starts paying off really quickly.
I'm kind of glad that the interview wasn't even an option, since we're based out of San Diego and it simplifies the logistics of our operations for not having to move to SF for a period. Having no idea of how NMX/NAB was going to go, YC seemed like the best way to get our idea out there whilst getting their great support system. Now, we can just go heads-down in development and prepare for our June release.
It's always extremely discouraging to get rejections -- we got rejected from EvoNexus[3], TechCrunch Disrupt NY, and YCombinator (twice). This pretty much tells me that I'm horrible at filling out applications. I'd like to think that if the YC partners had walked up and talked to us at our booth, we would have definitely gotten the interview.
This Vegas trip was the most amazing thing that has happened since I came up with the idea of pleenq[4], because we barely had to sell the product -- people were so excited by the possibilities it would bring, and about all the monetization opportunities it opens up. Most of our customers were referrals from others who had seen our booth, and were told to "make sure they saw pleenq before they left the show". I closed every single person I talked to at our booth over the 4 days of the show, which was basically the highest form of encouragement I could have hoped for.
[1] https://facebook.com/pleenq and http://pleenq.com
[2] Demo of PLEENQ that we showed at NAB/NMX: https://www.youtube.com/watch?v=4wu4gaiaA7I
[3] A San Diego-based incubator that takes 0% equity and is really great for startups with a little bit of traction
[4] Pleenq lets you tag items in any image on the internet and link them to where they can be purchased
I think something like this would help you focus your recruitment efforts on those who have at least contributed to the community in some way, which should filter out people spamming every single email in the thread.
Another idea is to mask emails with a craigslist-like mailing address, which would give the end-user the ability to report an email as spam, and therefore tie that email to the offending party's hacker news account.
Edit: What I mean is that each hacker news account would see the email address as a different one, so when they emailed that account it uniquely identifies the account that originally viewed that email address. So, Spammer A sees Poster B's email address as hn-49384932842@ycombinator.com, and Legitimate Candidate C sees Poster B's address as hn-4494838943842@ycombinator.com. When either one emails that address, if Poster B reports the email as spam, and if enough reports accumulate, the HN account sending the spam can be docked karma and lower them below the threshold allowed to view further posts.
-Financial debt, so all of your finances are inspected
-Family connections, so all of your family is investigated
-Marital affairs, so you're asked about it during the poly
-Pirating software, again asked about it on the poly
...and all sorts of other things. The big thing you hit on is that this isn't very painful unless you try to hide it. If you try to hide something and it comes out in the investigation, you'll almost certainly be disqualified.
I'm not saying this to be mean, but you didn't parse my comment properly, so I'll break it down.
>Although this department includes the military forces (minus the coast guard), the vast majority of its member agencies are all civilian agencies, and the person who heads it up (Secretary of Defense) is a civilian.
This department is referring to the Department of Defense. The next sentence refers to its member agencies, not the members of its agencies. The member agencies (the agencies that are a part of the Department of Defense) are mostly civilian agencies, which you can see listed out on the wikipedia page here: http://en.wikipedia.org/wiki/United_States_Department_of_Def...
In it, you'll see that there are 15 defense agencies, 4 intelligence agencies, and 3 military departments, for a grand total of 19 to 3.
> No, the person who heads it up is an Admiral in the Navy: https://en.wikipedia.org/wiki/Michael_S._Rogers The SECDEF oversees the DoD as a whole.
The "it" in that sentence is referring to the Department of Defense -- which was initiated by "this department". The person you linked to DIRNSA, which has nothing to do with what I was saying.
The foreign nationals question is a matter of seeing how deep your clearance process is going to go. If you're in Kansas and the only people you know are from Kansas and all of your Facebook friends live in Kansas, it's going to make it easy for the FBI agents (who conduct the clearance work) to do the required interviews. If you start listing foreign national contacts, each one of them has to be investigated individually (the ones who are close relatives), and that's a lot of work. It's basically easier to fail someone on that and hire the person in Kansas.
Now the same contracts are hiring people on at 40-50k, and people are taking the jobs because they already gave up their government spot. The contracting world has pretty much turned inside out because of the upheavals over recent years. Most of the contractors I know are aiming for government jobs now.
The NSA has nearly unlimited hiring potential with just the pool of military folks alone that work there. There are constant hiring freezes for a year at a time, because a lot of buildings are over capacity.
If one of these college students were to apply to the NSA through NSA.gov (mandated as the only way someone is allowed into the agency), they would have to apply a minimum of 2-4 times, because the application stays good for about 90 days, and the average applicant waits 6 months to a year to get accepted. This is assuming they're applying straight through without having someone with hiring power pull their application from the queue. After that, the process to get a clearance could take anywhere from another 6 months to 2 years (possibly more in some exceptional cases) and costs the agency about 250k.
So, it goes without saying that bringing onboard a fresh college student who isn't going to even get to walk through the door at least a year after applying, can pale in comparison to bringing on someone who already has a clearance and training. The article assumes that the NSA relies heavily on its external recruitment, but the vast majority of folks working there just change out of a uniform into jeans and a shirt.
I think what impresses non-technologists the most is if you have a full and utter grasp of their business, not just their product offerings. You can show great prescience if you can thoroughly research their products and say things like "I bet your customers have said that they wish they had x feature", or "Have you considered y alternate method to monetizing your core product?". Chances are, all the ideas you toss out they will have thought of, but it will show that you're in the business of helping them get to business solutions and not just build them some cool software. This will make them feel like you're on their team, and greatly increase the chance of landing a contract.
Consequently, if you find this part to be difficult (extracting the core business that someone is in from their product offerings) then it becomes more and more difficult to pitch technology solutions, since you're basically missing the whole point of their company and just attacking their pain points from the outside->in. Whoever is in the role of gathering contracts should be able to direct all of your technological forces into a business solutions package, instead of a technological solutions package.
davismwfl lists his email in his profile and gave you an open invitation to talk with him and especially soak up the knowledge that he has gained from starting two consulting companies. In an instance like that, you want to be the one contacting him, sussing out his schedule, giving him a few options for when you could possibly meet, and following up with him consistently when you get radio silence.
This is not meant to be an attack on your approach, but I read your response as extremely passive (easy to talk me into lunch, probably twist Hung's arm), and an aggressive approach where you actively engage an interested party is what will lead you to succeed in that role.
I understand that taking on that role might not be your forte, so you might be reluctant in fully embracing it. How I would approach it is by attacking the problem head on so you don't have to bring in a business development person who is a complete unknown within your group, and just trusting them to get the job done. Go to local meetup groups, and maybe even meetups within a 2+ hour radius. Troll craigslist for potential clients nationwide. Maybe even line up a couple projects with a freelancing website just to get the ball rolling -- projects that make economic sense (being able to complete a project with 2-5 of your man-hours for 500-1000 dollars).
I've thought a lot on this over the years, and the ways I'd personally fix this are:
1. If you're going to have homework in your class, have a policy such that if a student gets 85% or higher on a test, they don't need to do any homework until the next test.
2. Possibly have a system where homework doesn't actually count towards your grade, but only can help your grade. This would help those who don't handle the pressure of test taking well, and allow them to boost their grades up through the homework.
3. Have assignments that are longer form and more constructive, such as writing papers over a period of a couple weeks, where the student can turn it in at intervals to get feedback until they feel comfortable that the assignment is in its final form. For a class like math, have the student write a lesson teaching the actual thing that they're supposed to learn, and see if another student in the class is able to read it and understand the subject better.
4. The hardest one -- applying new concepts to real world applications that are in peoples' interest areas. I would have definitely perked up if someone had drawn comparisons of concepts to how they would apply to game programming, for instance (pretty much all basic math used in things like matrix transformations/linear interpolations, raycasting, inertia) which took me a whole lot of Khan Academy to start to understand much much after the fact. What makes this the most difficult is that the teacher has to be incredibly creative to pull this off, regardless of subject they're teaching. Can you imagine an english assignment being writing dialogue branches for an RPG?
My final GPA in high school was 1.85, which basically forced me into the military, forever changing my future. My end goal has now become to start a program in high schools where students are funded to start their own business, say for 10,000, and their absences of lack of completion of assignments are deducted from their funding. At the end, they'd basically get to keep whatever was left including what profit their business made. Still fleshing this one out, but I think giving students basic knowledge of how businesses operate through practical knowledge could drastically change their trajectories.
The lifestyle part of it is that 7 days out of the week, I wake up whenever my body wakes up and pretty much roll over to the computer desk and start working. I'm married (with no children), and although it took her a bit to really buy in on giving me uninterrupted development time, I finally have that for most of the day. I pretty much do this until 9-10pm, and then my wife and I catch up on TV shows or watch a movie or two.
There are, of course, minor distractions throughout the day like reading HN, or playing a few iphone games. In order to combat that, I hold off on doing anything like that until I hit micro milestones on my current task.
As far as money goes, I left my full-time job in order to work on this idea, so there's absolutely no income until I start generating it from customers. I'm borrowing against my house to pay the bills, but that's how much I really believe in what I'm working on, and I've intentionally forced myself into this position because it makes me prioritize everything as if my life depended on it (which it does).
It has a screencast feature that lets you create a video (which you can crop to whatever part of the screen) and then uploads that video onto their server and gives you a shareable link of the video.
At my last job, we used to use that for all of the bug reports, because it's a thousand times better than what you reference (taking multiple screenshots and having to explain exactly what's going on between them)
Here's an example of me using the program to get to this comment: http://screencast.com/t/zbfcEinhJN
It can be a little slow and wonky at times, but a lot of good (free!) features out of the box.
The leap from making money to making absolutely nothing after having just gotten married in October probably looks like the workings of someone who has gone completely bonkers. Even though it's a terrible time for me financially, I feel like it's the best time for my business to take root and thrive. I owe a lot of how I think about this transition to the hacker news community as a whole, since there is a direct correlation between the time I started reading hacker news, and the time I started dreaming of owning my own successful company.
I don't have a landing page set up yet (man there's so much work to be done!), but if you're interested in knowing when Pleenq goes live, send me an email at justin@pleenq.com and I'll add you to the first round of invites!
The other posters within random comments are also conflating the watchlist with the no-fly list. I don't need to go into details about the differences, because their names say it all.
(Source: I built one of those data interchange legs, and worked a lot with the TSC)
There are a ton of positions open including: Node/PHP Developer, Devops/Sysadmin, Front End Engineer, Graphic Designer, and other non-technical positions. Here is the link to the job listings: http://www.thecontrolgroup.com/category/job-openings/
Here's what the listing for Node/PHP Developer says:
San Diego application developers! Are you looking for a job where you’ll feel challenged, be appreciated, and given the space you need to do your thing? We’ve cultivated a developer-friendly culture here and we intend to keep it that way. You get autonomy, and the chance to collaborate with other top-tier developers in the industry. Sound good? Keep reading.
Do you view programming as “your craft” and have strong opinions on the subject? Are you prone to raising an eyebrow when people say “Big Data” and enjoy playing with stats? Do you live in the cloud? Do you dream in data structures? Do you want to gain experience scaling a high traffic website to handle millions of requests each day? If you answered “yes” to any of these questions, we want to hear from you. To Apply, You Must Have:
*Experience with node.js
*Expert-level JavaScript knowledge
*Solid experience with PHP or Python
*Solid experience building scalable web applications using open source technology
*Knowledgeable in HTTP / DNS / INET protocols
*Strong understanding of web standards-based HTML5 / CSS3 / AJAX coding.
*Confident in a Linux environment using bash and vi/emacs
*Use a design pattern when you can and write reusable code
*Have used MVC (Zend FW / Codeigniter)
*Use Distributed Version Control
*Familiar with functional programming languages
We Would Be Stoked if You Also Had: *Experience with Redis
*Experience with Nginx
*Experience with Internet marketing and split testing
*Knowledge of eCommerce, SEO, and affiliate marketing
*Experience with Elastic Search, Lucene, Solr, or Hadoop
Freelancers! Please Note: This is a full-time, onsite position. Sorry, you can’t work from home in your PJs.In exchange for showing up to work and being awesome every day, you’ll get tons of perks like:
*PTO
*A generous compensation package plus 401(k) plan after one year
*All the Red Bull and coffee you can drink (which leads us to our next perk)
*Health care for when your body rebels against all the Red Bull (including dental)
*Freshly squeezed veggie juice every day
*Snacks galore
*Early bird breakfast on Fridays
*You have access to Xbox, Call of Duty, Halo, and free throw basketball machines
*Working in a state-of-the-art office right on the beach, or in the heart of Little Italy
*(Most importantly) Awesome friends and coworkers
------------------------------------------------------I work in the Pacific Beach office which is literally right on the beach -- it makes for really awesome lunch times being able to walk the boardwalk and try a bunch of different places. There's even a rack at our entrance to put your surfboard!
You could talk to me if you're interested (justin.mealey@thecontrolgroup.com), or you can apply through our website.
As far as the predictability of someone's aptitude, the DLAB was a good baseline to show that a person had better language acquisition than the average student. When students barely met the baseline of 100 points on the test, they had an incredibly tough time in the beginning with a language as different from english as arabic. What the test didn't measure, however, is a person's will to persevere through the slow progress, constant mistakes, and utter frustration. Although the low scoring students had a tough time in the beginning, most of them passed in the end. The student's that ended up failing out of our class were, ironically, the students that did exceptionally well in the beginning. I mostly attribute this to them relying on the ease of understanding in the beginning, rather than studying at the level that the lower scoring students had had to learn how to do when they had started out.
Language learning is not a linear path where you can acquire x amount of words per day. Your language learning is affected by so many factors such as sleep, healthy living, happiness, motivation, among others. There also seems to be a point for almost everyone I was with where constant study results in a moment of clarity, where you start to believe in your skill in the language and lose the fear of failing in conversation.
All in all, I would say that learning a language is almost exactly like learning programming. The material to learn either is readily available on the internet, and each purely depend on your desire to learn them. There will always be those that just can't quite jump high enough to get past the initial hurdles, and that's what these tests are there to provide -- a way for them to get filtered out before money is invested in their ability. In that, it's similar in a way to giving someone a fizzbang test. It won't tell you that you have a great programmer, it will just give you a baseline assessment that you don't have someone that shouldn't be a programmer.
The key point is this: the NSA does not create policy for its operations. Those are written into law through executive, legislative, and judicial processes, and the three should theoretically balance each other out, which the public currently deems as not doing a sufficient job of balancing. The NSA acts as an instrument -- the employees (to include the director) are directed through a system of reporting and feedback, and determine how best to act in order to obtain more positive feedback from customers of the reports.
This isn't some theoretical system I'm talking about -- it's a database of reporting with attached feedback. The feedback shows who consumed the report, whether or not the party found it useful, any enclosed comments about the report, and how high up the report went. If my report made it into the president's daily brief and more information about the reporting subject is desired, that will show up in the feedback, and thus I have my "direction".
How does this translate into real world operations? Here is a theoretical conversation between Mr. Policy and Mr. NSA:
-----------------------------------
Mr. NSA: Here is some information I found about country X, which might indicate that they're conducting operation Y.
Mr. Policy: I would like to learn more about operation Y, and country X's intentions to expand it.
Mr. NSA: I don't currently have the capability to expound upon operation Y, unless you grant me the authority to access datastore Z.
Mr. Policy: We took a vote, and you have access to datastore Z on a thirty day trial basis, but then must shut down operations if nothing of value is found.
Mr. NSA: Here is the information you requested about operation Y and country X's intentions.
Mr. Policy: This information was not useful in directing policy, therefore datastore Z is to no longer be accessed.
-----------------------------------
From this, I think you can extrapolate my point. Do you blame the scalpel for being too sharp, or the surgeon for handling it incorrectly?
In a way, I tend to believe that the clash between the older programmers (who tend to intricately understand the underlying components that they manipulate) and the newer programmers (who have tend to be able to manipulate a lot of the built components much quicker) comes from the crossing of this philosophy threshold.
As far as the original article is concerned, the point is that we shouldn't just be following one philosophy or another just because some people that might be more intelligent than us created it (directly against this comment). You can cherry pick what paradigm works best for you in whatever situation you find yourself in, and change it if it's not working out as expected. It is exactly one's own skill that determines whether or not the philosophy one selects are correct for the situation.