But, I suggest that you initiate a local campaign to pressure Mercantile to make the process easier. Here are few ideas to consider -1. Bring this to the attention of Computer Association of Nepal2. Share this tragedy with tech-activists (Gaurab Raj Upadhyaya, Brijen Joshi, Bhupal Sapkota, Ankur Sharma, Akar Anil are few names that come to mind) and get their help raising the concern to the wider community (blogs, meetings etc)3. Meet with Mercantile management to make sure they are aware of the current hoops and communicate how backward the current process is. Also make sure they are not being asked to make it this way from govt. agencies. Offer help if they need it.4. Meet with government representatives and request them to facilitate the needed change.
Email me if you need intros to people I mentioned above or if there is anything else I could do.
Although, to spare yourself future problems, you could register nepalesefreedns.net and have people point nameservers for their .np domains to nsX.nepalesefreedns.net. Set up XName or a similar panel for it.
That way you will only have to endure the pain once. That is, until the registry breaks something else.
Not as bad as your problem but a mild annoyance nonetheless.
Would that be viable?
What also sucks is being asked for money to change name servers only:
.gr: 46.64 (74 USD) .cz: 14.57 .dk: 24.29 .hu: 17.49 .ro: 17.49
Another issue might be that the genuine poor who most need cars are those that use them - all day every day - to go to and from their low paid jobs. If you intend the cars to actually be shared you'll have to choose a way of addressing that.
The hazard I envision with ZipCar-lite is not only the monopoly the other commenter raised but also incidental costs (gas, accidents, etc) unless your plan is to subsidize those items, too.
Best wishes for your project, it could be great!
ashamed of: the Dark Tower series
tech: no interest in reading one from cover to cover, but I'm open to being convinced otherwise
edit: not sure which way I interpret "ashamed", take it how you will!
Ashamed of the title: Yoga, Inc
Tech book: CSS and HTML Web Design (because I've been faking it all along)
ashamed of: The Neuromancer, W. Gibson
Tech: Lions' Commentary on Unix, J. Lions
FWIW, I'm interpreting this as "ashamed to admit you haven't read this title yet" as opposed to "ashamed to admit you want to read this title".
To Look Smart: Wolfram's A New Kind of Science
Ashamed Of: Structure and Interpretation of Computer Programs (SICP)
Tech: Knuth's The Art of Computer Programming
To be fair, I've not read these books; I attended a lecture of his at MIT, and he seemed to really know his stuff. If I wanted to study DB implementation, I'd start with his writings.
2. You probably mean minimum, rather than maximum.
3. I got that down to 0.05 s (50 milliseconds) by using two fingers on an iPad. That took about 30 seconds, and I also got a .06 in that time, so it probably can be improved upon.
2) A really good text to speech app for news so I can listen to it in my car
I can't think of a third right now.
I would guess Amazon, Facebook, or maybe a big Chinese corporation.
The patent portfolio will likely go to the highest bidder, independent of any company assets. No one needs their devices or the OS. Google, Microsoft, Apple, and Samsung are all candidates, or it may go to a consortium of some/all, as has happened in the past with the sale of Nortel's portfolio.
So Scneier's blog is down and we can't tell if it is a freak outage or if it is an outside party. Scary times.
The site above does not check for https URL's.
Pick a simple chore you do now manually by hand and try to automate it so that the computer can do it for you.
This way, you may have more motivation, because if you can automate the chore, you won't have to do it manually anymore.
Learning to code from the "how-tos" is hard if you are unmotivated because the examples they ask you to create are not something you'll ever need, or use, again. Therefore you have difficulty staying motivated because it all feels like busy work.
Note, the word "simple" above is critically important. You have to pick something that is within your skill level. So it has to be something "simple".
I'll ignore the obvious question of "why are you trying to do something you're not interested in?" because that's not what you're asking. I think most people are terrible at motivating themselves to do something they're not interested in, so the trick is to find a way to hack that.
I've seen so many people decide to learn to "program" because it was part of their Computer Science degree which they chose to pursue because that's where the jobs are. Many of them finished their degrees and ended up in a "software factory" churning out code for as long as they could stand to do it.
I don't see programming as an end unto itself (that "job" is not going to make you enjoy programming; it'll probably make you hate it). It's a skill that allows you to make things. To manufacture interest in programming, program something to enhance something you are interested in. Stick with easy things -- something you could learn to do from an hour long tutorial in your language of choice (and stick with an easy language). Don't stress over building something that is "right" or even attempt to understand best practices at this stage. Doing so will probably result in loss of interest.
Once you've made something that helps something you're interested in, the positive feedback from that experience might challenge you to look at more complicated tasks, further honing your ability. At some point, you'll encounter a problem that will be complicated enough that you'll have to go back and learn how to do things "right", and you'll probably be far enough along in your pursuit that you'll enjoy learning how to do it right.
I've done this myself with a few skills I wanted to pick up. I've always wanted to get into hardware, but could never manufacture the interest. Recently found myself purchasing an Arduino and a bunch of mysterious parts to make a device that will send me and my wife a text when the dryer completes its cycle. My interest in doing this was for task avoidance -- I hate ironing.
Why are you trying to force yourself to do something you aren't interested in? My first suggestion would be to really understand what you want out of it, and why you are doing this.
My second suggestion, if you decide it is something you really do want to do and you have a good story for yourself as to why you are doing it is to try to do learning with either a co-learner or a mentor who understands your motivation for learning, and to try to work with them to find real projects to apply what you are learning that relate to your motivation.
For this specific issue, I suggest you go to programmer meet-ups and make friends in person. Find someone you hit off with. Ask them to do a little hand holding and explaining. You might have to try this a few times before you find someone that clicks with you in the right way. Once you get over that initial hump, you will likely be fine.
Check out how my first project looks now: http://sudokuisland.com
There are now several thousand lines of code, both front end and back end. I can build handle all parts of the stack. The learning process took over a year but that was while working full time.
As much as I can't praise Udacity and Codeacademy enough, they aren't enough. Without a project you will forget everything you learned. I know my code inside and out, and can refer to it when I see a similar problem.
In short: why not sit down and try to code something simple?
A) It's better to give 100% for 30 minutes then 70% for 60 minutes. 30 minutes a day is a small commitment even for those with lack of motivation.
B) Don't judge your practice by how much you've accomplished that day but by how successful you were at "practicing perfectly" for your allotted time.
It is exceedingly difficult to just "learn to program". If you were to go to college then you would be set tasks that you would be motivated to complete (for a qualification of what have you) and you would thus learn enough about programming to complete the task.
Without the motivation for each stage of learning - the task of learning would be pretty dry.
1) Programming is not the "the literacy of the 21st century." Come on. It isn't now and it never will be, unless languages evolve to be essentially AIs that you can just request features in English, and even then it won't be, since most people won't bother to make programs. I'll go to the mat on this one. Those who bandy this idea around are misrepresenting reality.
2) Dan Miller, a career guru/author, has a point in one of his books that you should not attempt to strengthen your weaknesses--because then you end up with "strong weaknesses". Instead, strengthen your strengths. If you are good at soft skills, selling, design, idea man stuff, DO THAT, and leave the Model View Controller stuff to those who live and breathe that. You'll (likely) never do it as well as they do, anyway.
3) If you insist on learning to programming despite these two admonitions not to, I agree with many here who wrote: pick a project, and do it. And not some dopey toy project that you don't care about. Something real. I had an idea for an application years ago and have been working on it in my spare time and now feel that I can program, at least to some level. If you are in a company, work with the tech people to contribute to one module or one class or one feature, and start there. Become master of that section, and then move on.
That said, there is something to be said for just diving into the deep end, especially if you have a real world use for some software. Engineers and Scientists tend to learn programming this way. They download EPD Python or iPython, grab some experimental data, and start writing analysis tools to give meaning to their raw data. Is there something in your real life where you could solve a problem with software? If so, then relentlessly working on it a few hours a day will get you to your goal. And remember, real software developers use Google. The blogosphere and sites like StackOverflow are a developer's friend.
You need an actual task to achieve and you need to want to achieve it, otherwise why bother?
Forget about learning to program. Figure out what you want to make, and start making it.
I've been working on an Android app recently. This is my third or so attempt at learning the platform. This time, I've actually made good progress, because I have a goal. I started not by saying "Gee, I want to learn this", but by saying "Why does this app not exist? I could make it. I should make it"
Start with a basic "Hello world". After that, instead of going onto the next chapter, think "What's the easiest thing I can do next to advance my goal".
The best way I learned to program is to do it. No,seriously. Pick a project you want to make and make it. If a task like "user registration" is too tough, break it down further into subtasks e.g. create form to register, have form send info to db, etc.
Following tutorials and online sources that have you make useless things like "CREATE A CALCULATOR" I never found useful in trying to learn programming.
After reading 2000 books on the matter, python and all the stuff I learnt only by before having the need to build something.
When I found out I wanted to build something, I started to understand coding. When I found a stopper I went back to the books, Google, and so on. At the end, I built the product I wanted and learnt to code. I think it's the only way to motivate yourself and learn how to code.
If latter, and if you really want to be coding for the love of it, get real serious and focus. Figure out what area (systems ? web ? mobile ?) and just code. If web consider devbootcamp.com. Otherwise get a book and write code. I'm not a huge fan of online tools. Coding is like driving. The more you do, the better you'll get. No one can teach you.
I know the feeling with having trouble working through books. Quit trying to pound a square peg into a round hole. Find what works for you (your current approach doesn't!)
Don't learn/read things just because you think they are good for you. Do what you are actually interested in.
If you're joining a team, be very clear about your abilities and limits so they can resource properly.
Find people who need a break and chat to them about what they're working on, what they do normally. Again, meet people.
Talk to the sponsors, even if you don't need help. Those guys/gals are usually rad.
Presentation matters. Practice yours.
Focus on what is essential vs. What is nice.
Focus on your strong suits. Have an artist doing visual elements? Build the visual interface first.
I have used gmail to date simply because I must have a synched service between laptop and mobile. So gmail was just there as a IMAP/SMTP server for the iPhone mail reader
However as pg has pointed out, and the pretty good ActiveInbox implemented (hey ActiveInbox - apply for YC!) a mail inbox is really a task list.
And it must be linked to a contact book. All of which must be integrated at the event level.
So which mail client I use is less of the question than how do I solve
* capturing and synching contact details, contact events, email messages and tags across all these
I have a workable solution in gmail now, but I cannot capture events on my iPhone. Android appraently does so I will switch but its not all tied together neatly.
I have played with mutt and goobook but frankly I can see a good couple of weeks disappearing down this rathole. Yet it should be a solved problem. VCards, iCal, X-Headers, the solution is there. It just seems there is no RFC we can agree on
my rant on this subject: http://blog.mikadosoftware.com/2013/09/17/help-i-cannot-find...
Edit: am I just ill-informed (!) or has there really been no successful standardisation for "managing contact details events and tasks in a mailbox?"
I use gmail, yahoo mail (through an extension), connect several pop3(I tell it to leave messages onn server), imap servers for work (for which emails are occasionally harvested and sold to spammers somehow..) and my own mail server (Hey, I am a web developer. No excuse to not have a el cheapo vps with webserver and an email servers combo), local maildir and mbox delivery for testing crap I write, several newsgroups and a shitloads of RSS/Atom feeds. It also has some xmpp integration of dubious usability. I also have Lightning extension which is supposed to behave as a calendar but I am a disorganised person and rarely check email by contemporary standard of every five minutes, whole day. Oh, and local spam detection.
Sure I look forward to Mailpile (just checked the marketing blurb) which promises to not show me ads and perform faster than "cloud" while offering all the features that should exist in practice to justify calling itself an email client. Competition is good and thunderbird is going senile by every passing day anyway.
I hope they won't spin off their custom web server as a standalone project too.
I've just always felt that a desktop client just adds another layer where things can go wrong.
From there I read it with lumail, if I have problems I revert to mutt.
I've got webmail setup for those times when I'm travelling and cannot use ssh.
Thunderbird was the first client I found that let me manage multiple separate accounts through the same interface, receiving and sending mail from each in a logical way. There's probably other ways to do that now, but I'm terrified of upsetting a system that Just Works.
Since it's within Emacs there's great GPG support, familiar keybindings, and less contextual shift than switching to a browser. It's also fully searchable, usable offline, and non-blocking to other emacs operations.
As a founder there are a few different issues that I see us dealing with. 1) finding people, 2) parsing though the people we find, 3) finding those worth talking to, 4) finding those worth risking an offer to. Which problem are you saying you figure out how to solve, each has its own unique dilemma to solve.
There may be some companies with biases that will prevent it, but there are plenty of companies that don't care how old you are, what you look like -- just that you're really good at what you do.
But be aware that many people overestimate their abilities or undervalue the judgement that years of experience bring. There's a lot of value in having been around long enough to see things come and go. To have made lots of mistakes and learned valuable lessons. Some people really are so good that they can skip much of that, but it's very rare. The only safe bet is to assume you're not one of those people.
And I wouldn't get too hung up about titles. If someone wants to call you "Junior Dog Walker" but pays you and treats you like you want to be treated then don't worry about it.
Youre interviewing at the wrong place, with people you shouldnt work with. When leveling a candidate two things matter, technical knowledge & leadership. Ive literally never heard anyone suggest leveling a candidate based on work history. Experience might affect comp, or indicate retention issues, but it _does not_ affect leveling.
To qualify my argument Ive a decade of experience. Ive been in "senior" roles for the last 4. Ive worked in a couple 4 man llcs, and a couple multi billion dollar tech cos. Ive probably done a hundred interviews, and ive coworkers in the hundreds and thousand range.
This question makes no sense to me, nor does your history of posting questions on here.
Based on reading your past questions, looks like you were not a good interviewee and/or lacking in real technical skills.
Communication is the biggest key to getting any position. You need to be able to sell yourself and your abilities. Can you explain what the basics of OOP, MVC, SQL, etc? An inability to communicate these terms, invalidates your technical skills. If you can not explain what an does MVC, how can you implement this pattern into a web app?
You could not articulate common terms that were used in programming during your interview process. At other times, you write about how you can barely program anything outside of a simple app/CRUD, then a bit later are bitching about how simple these tasks are.
Focus on learning how to communicate the terms better. Every profession as certain terms and ideas that they use. Nursing has them, engineering has them, and teaching has them. Programming certainly has them. Sit down and learn the terms.
I would think go the showcasing competitive route, hackathons, open source projects, etc. If you can make a spectacular showing there and win the kudos of your peers, that would account for something.
Bear in mind also that even though you've never heard of an audit of GPG, GPG is actually a pretty high-profile target. Smart people have already looked at that code pretty carefully.
Since GPG is an open source project, a better approach would be to find a way to sponsor a bounty for vulnerabilities in GPG. But here too you'll run into problems:
* It will take fo-re-ver to adjudicate what does and doesn't qualify as a serious finding. Google and Facebook manage this problem by hiring very smart vulnerability researchers and allowing them to come up with criteria pretty much by fiat. Here, you're going to end up in a 2-month-long argument about whether man page bugs are vulnerabilities because of the nature of the project.
* Output of these programs is nonlinear and unpredictable, so it'll be tricky to figure out how much money needs to be set aside to satisfy reward payouts. In the meantime: who holds that money? And where does it go when the bounty outlives its utility?
If you really want to do some good, consider starting a project (which would require no funding) to either:
(a) Build a replacement GPG in a more modern development environment, or
(b) Annotate all of GPG's source code.
Here's an overview of GnuPG's committers:
Werner Koch: 2677 commits over a period of 5764 days. David Shaw: 1197 commits over a period of 3807 days. Marcus Brinkmann: 202 commits over a period of 3753 days. NIIBE Yutaka: 53 commits over a period of 641 days. Moritz Schulte: 39 commits over a period of 1756 days. Timo Schulz: 29 commits over a period of 896 days. Stefan Bellon: 21 commits over a period of 765 days. Repo Admin: 9 commits over a period of 2634 days. Andrey Jivsov: 8 commits over a period of 37 days. Ben Kibbey: 6 commits over a period of 20 days. Neal Walfield: 5 commits over a period of 1 day.
This doesn't negate the need for a code review of some sort, but it does suggest that it would be difficult for an outside agent to silently introduce changes in master without the core developers noticing.
Word on the street is the code is horrific and last I checked was not even checked into git, in any way, yet.
Could be for example just a simple message "Audited, file: aaa/xyz.c, checksum 3ea1b.. revision 1c030.." signed with auditors public key.
Another thing you can do is attack real world problems,there is a shocking amount of bad data science out there.See:http://www.slate.com/blogs/moneybox/2013/04/16/reinhart_rogo...
Regarding the degree, credentials are important (and imperative if you want to direct your own research), but one option is to start out by contributing to an open-source project. If you have a specific area of scientific interest, then be strategic and find a project in that area. To take biology as an example, I would look at something like CellProfiler (they are on github!). Also read the papers published by that lab to get a sense for how the software is used. There are many other open-source scientific software projects, and contributions to a project could give you a foot in the door to employment as a developer in the field.
1. _Stats: Data and Models_ by De Veaux, Velleman & Bock
2. _Fifty Challenging Problems in Probability with Solutions_ by Mosteller
Basic data analysis:
1. _Python for Data Analysis_ by Wes McKinney
3. _Exploratory Data Analysis_ by Tukey
4. _The Visual Display of Quantitative Information_ by Tufte
- R & ggplot2 & (Sweave | knitR)
- Python & numpy & pandas
- UNIX tools (https://news.ycombinator.com/item?id=6046682, https://news.ycombinator.com/item?id=6412190)
- basic SQL (https://schemaverse.com/tutorial/tutorial.php)
- data visualization: (R & ggplot2) | (Python & matplotlib) | d3.js
- OPTIONAL: C/C++/Java for hardcore Bayesian stuff, Julia for being cool, Fortran for specific academic domains
On getting people to take you seriously: If you knew the stuff up there, I would take you very seriously, even without the STEM degree. You can pick this stuff up outside the classroom (in fact it might be hard to find uni classes that cover this stuff). So if you did self-study, and blogged about it or something, people would take you seriously (esp. if you got good at something "hot" like d3.js or Bayesian). In fact, given your background in web / software / business, you could be considered even more valuable (by web / software / business people).
What are you interested in specifically? Where do you want to end up?
Also Teddy Roosevelt's biography has been very influential.
I still remember how he told me in 2005-06 that 3d printing is going to usher in a whole new idea of what work should actually be. I was a engineering student at the time, quite obsessed with the room-sized 3d printer and could not fathom exactly how that would happen. Well I guess it is starting to at least.
Zen and the Art of Motorcycle Maintenance
How to Win Friends and Influence People
[And from your Jahreslisten: the Bible.]
Fierce Invalids Home from Hot Climates, Tom Robbins
Homage to Catalonia, George Orwell
Catch 22, Joseph Heller
Timequake; Mother Night, Kurt Vonnegut Jr.
Seven Pillars of Wisdom, TE Lawrence
The Histories, Tacitus
The Catcher in the Rye, JD Salinger (caveat, it was most effective when I read it at 16)
Redwall, Brian Jaques (got me really excited about reading when I was in the fourth grade)
This list could be much, much longer, but those are the most prominent 'life-changers' that come to mind.
Carlos Castenada's Don Juan series (yes, I know it was fiction) - "one has no choice but to believe. What matters is what you believe".
John C. Lilly's "Center of the Cyclone".
These three, all around early-mid 70's, ended up moving me from the UK to Los Angeles. Strangely, each adds a different understanding to the others. Together, I guess it just makes me a bit strange. But it works.
Machiavel - The prince
Then technology improved and in particular someone invented the SCROLL WHEEL which makes scrolling on the web much more convenient.
My preference:When presenting a browse experience where the user does not know what he wants, and is just exploring, use scrolling. Make it easy to "discover more", and make it immersive UX.
When presenting search results, or anything where the "user knows what he wants", use paging. This allows user to scroll back and forth on a page to "find what he wants" and click next to go to next page.
You can mix both to present a better UX. E.g paging for search results on 2/3 and scrolling for "related / similar / you might like" on 1/3 side bar.
Also take a look at TNW.com. After reading one article, it auto scrolls the entire list page which makes it easy to browse the categories + articles which is neat.
And if you're designing for mobile, paging is painful and it almost always has to be scroll - design for the thumb.
so obviously if the user needs to bookmark or get back to a specific listed data point quickly pagination will be a superior pattern choice. User : "I need <x> and I know it's on page<y>"
If the order of the data is important it can go either way. Both scroll and pagination allow for this. Scrolling is advantageous because it does not limit the viewable data. While pagination allows the user to jump around the set in a predictable manner albeit with more clicks. If there is an indeterminate amount of data I think the point should go to the scroll pattern.
if the dataset is constantly updated or re-organized hands down Scrolling will be a better solution. recalculation of pagination on rapidly changing data sets is a nightmare The user's mental position in a set will be challenged and getting through the set can be complicated and take many clicks.
Scrolling becomes much more useful if there is some form of visual aid with the information being listed. Google image search is a pleasure to scroll because the set that I am scrolling through is changing giving me a natural feel of exploration.
Pagination is much more effective on static, well organized data. A phonebook makes sense to have an index. each page could be a letter allowing the user to quickly jump from section to section based on their needs. A scrolling pattern could take hours to get to the desired data with a huge volume of numbers/name pairs. Without pictures, it also requires the user to read more which could potentially further slow them down.
The patterns are not mutually exclusive. Take for instance the phone book example mentioned above. Add pictures to each user and then have multiple scrolling pages paginated by letter. This would combine the strengths of both patterns minimizing the user's need to explore, but also offering an interesting way to explore a directory.
Scrolling: spirit of exploration. Low level of interaction. Great when the user is only generally aware of what they need. Poor for searching using the UI (great for find on this page)
pagination: ordered targeting searching. Enables quick navigation, eases return trips to info. Poor exploration. disjointed for reading. High level of user interaction.
All said I really enjoy scrolling. I find it relaxing, Seamless when reading articles, and it frankly feels more natural to use. I think there are good ways to use pagination, however I feel that I see it used inappropriately more often than scrolling.
(No, I don't want to click through 1,642 pages to view your article or list of top X things!)
how about long-form matter?
e-books in particular...
A wholesale computational model of the cell is an incredibly ambitious task to achieve via a broad, unfocused approach to building a chem-concentration database.
The main issue they would face is in your bullet #1: What is your "Pagerank" for cell structure and chem-concentration analysis, what/who do you put your weight behind?
How do you merge these data sets? This research is distributed in labs all over the planet with different quality standards, research objectives, lab conditions, data hygiene, statistical significance, etc.
What you've written seems like a plausible approach in a pure research setting within a single lab, but if their end goal is a computational model of the cell with commercial side-effects along the way-- the best way to achieve that would be to chip away at it piecemeal. Not through an unfocused merger of cell "big data".
E.g. identify specific protein binding sites and conformations that correlate with a specific type of breast cancer, track their conformations under different conditions--- prove that your data is superior to data yielded by existing models.
Of course, you would also have to monetize somehow.
The specific thing you chose is less important than not attempting to paint the whole model at once.
> (1) would improve therapies across the board for all major diseases at once
How? Unless if by "at once" you mean they would begin the era of using this approach on any disease. But surely each disease will have its own puzzle.
- he really doesn't use his PGP key all that often, had the same one for 16 years on god knows how many computers, and decided that if he's going to generate a new one, he might as well send a message with it.
Edit: I am located in the North Eastern part of the US.
Edit 2: perhaps we need a geolocation aware social network a la Square but just for notifying you of other nearby PGP users...
He has worked previously in mostly corporate and private context, so 2048 is just fine. Now he works with people and data NSA wants their hands on and he wants the data to be secure also in the future. It's just reasonable to move to 4096 key sizes.
>Dr Lenstra and Dr Verheul offer their recommendations for keylengths. In their calculation, a 2048 bit key should keep your secrets safe at least until 2020 against very highly funded and knowledgeable adversaries (i.e. you have the NSA working against you). Against lesser adversaries such as mere multinationals your secret should be safe against bruteforce cryptoanalysis much longer, even with 1024 bit keys.
See also: http://www.keylength.com
> 3) Assume that while your computer can be compromised, it would take work and risk on the part of the NSA so it probably isn't. If you have something really important, use an air gap. Since I started working with the Snowden documents, I bought a new computer that has never been connected to the internet. If I want to transfer a file, I encrypt the file on the secure computer and walk it over to my internet computer, using a USB stick. To decrypt something, I reverse the process. This might not be bulletproof, but it's pretty good.
- Don't ask my to sign up or give you personal info without giving me a good reason; let me see a demo or at least something like screenshots/results/examples first. Related: what am I getting out of taking time on your site and/or letting you know about me? Do I trust that you'll deal with my personal info in a respectful manner? (Hint: No, I don't.)
- If you are not a native speaker of English, then run the site by a native speaker before publicizing.
Concerning the first two above: even when you've paid attention to them, you probably haven't done nearly as good a job as you think. I come to your site knowing nothing about you or what you've done; help me understand.
For example, you say, "Unclear message about why I would use said app". Sure, make it clear. But first, pay attention to a more fundamental question: make sure that your site indicates that it is about an app. And be clear what platforms the app is available for. And how to get it. And does it cost something. Etc.
(Idea: Find someone who knows nothing about your project, show them the site, and then ask them what they think it's about. If there is a sign-up, then ask them if they noticed it. Ask them what they think they get out of signing up. Don't give them any hints beyond what they already saw on the site.)
The only thing you should would worry about is making sure if there is a spike that your site doesn't crash.
The other things you're talking about are not optimizing for a Show HN, they are optimizing for a successful landing page.
A well researched "sins" list in this area might make a great addition to the "Guidelines page" - but there again a poor post is probably an effective indicator for the quality of what is to be found.
Even posts that garner many response of "No demo?", "No screenshots?" frequently gain responses than the few things I've posted. (e.g. Console mail client with lua scripting, sysadmin tools, or my updated blog-spam detection service.)
1. Not sure HN is the best place to ask this. Yes, there are plenty of start ups here and entrepreneurs, however, they are all busy just like you finding ideas
2. Go where business owners hang out who don't necessary have the tech skills in house to solve their problems.
3. Start smoking cigars
I pick up a cigar every now and then and head over to any nicer establishment with a good bar, good scotch, atmosphere and where people mingle.
1. The people I meet at cigar places are typically business owners...and not in tech. They own manufacturing businesses, finance, retail and other low tech brick and mortar type businesses who have a need for tech but typically none in house.
2. Cigar smokers love talking to other cigar smokers, even when you are a complete stranger. Also, smoking a cigar takes 1 - 2 hours...so you got them pinned. Start the conversation soft, casual...just like dating. Then start finding out more about them, what they do. Ask some simple questions about their field and let them explain as if they are pure genius. Start talking about their business...and now you start narrowing down on problems, issues.
I do this all the time. It's amazing what you can learn...and they'll love to tell you about it because they are having a good time smoking cigars, sipping scotch and hiding from the wife.
I just recently spoke to a small retail owner who has a chain of consignment stores with a number of POS systems. Buying a POS system isn't a problem, it's doing the financial reporting and consolidating data from multiple locations. He had been looking for quite some time and couldn't find anything good that actually could understand that data came from multiple locations, rather than multiple POSs inside the same store. He also had a huge number of different SKUs since no item coming in is the same as any other in a consignment store. Who knew...I would have thought this was a solved problem. It's a totally un-sexy space but I really think this is where you'll find you best ideas.
This works better than asking people what their pain points are. For heaven's sake, if you want to know what someone really thinks, asking them is often the worst approach to take!
I started it a few years ago with zero web design knowledge and have learned a bunch.
basically I am a computer tech and it was a pain in the ass to keep up with all the good software that I used so I solved it by building the freeware index.
at this moment there are 2 ways to get the entire index and one of them is via a Google spreadsheet. I recently discovered Google script and wanted to use it to expand the spreadsheet. with Google script I wanted to create a linkable row or sheet instead of the entire spreadsheet. Or somehow separate each sheet into a neat page on the blogger site I put up tariqghrayyib.blogspot.com.
the only reason as to why its so small is because I have restarted the project at least 4 times from scratch and this is the farthest I have gone so far simply because I made the subreddit where I can get more exposure.
if anyone knows Google script and can help that would be beyond awesome