Some downsides:Performance is not great.Lack of coherent data architecture (e.g. Redux).Difficult to manage state change (as opposed to React) due to a more limited programming model - e.g. template ifs and repeats don't know to reevaluate in many cases. This makes it harder to integrate with third party js libraries.Inferior tooling vs React.
Philosophically Polymer is more about the DOM and React is more JS-focused. Some of this is personal preference.
Polymer is made of magic. It uses magic cutting-edge browser features where available, and where they aren't it fakes them using magic. Some of its APIs like Polymer.dom(x) are completely magic. When it works, it works really well. When it doesn't you are going to waste so much time trying to find out why.
A few commenters mentioned poor browser support, but we haven't experienced any problems other than IE<=10.
In many ways Polymer is just a shim for the WebComponents spec with data binding added in, along with a standard library of web components. The resulting framework-style is basically plain-JS/HTML with a la carte use of Web Components where appropriate. Unlike [my perception of] React or Angular, you can use Polymer a bit without going all in. (Ironically the one thing you can't currently do is mix Polymer Elements from Source A with Polymer Elements from Source B at runtime if they have common, but separately hosted, dependencies).
WebComponents feel a bit like Java swing, in that making HelloWorld is high overhead, but once you've got a nice toolbox of components going, you can pull them out and use them flexibly. This is not unlike React components, except Polymer/WebComponents use an HTML-centric definition format while React uses a JS-centric definition format.
That means without shimming other libraries, polymer is incompatible with any other libraries you might use to manipulate the DOM. For example, you can't easily mix angular, react, or ember templates with some polymer elements, because (e.g.,) angular's ng-if directive doesn't use polymer.dom to inject created nodes.
This is currently my biggest beef with polymer. Someday, webcomponents will be great, principally due to composability and portability. Just plug the one component you need in to your extant work. But for now, that promise is not quite realized.
Also it is over-complicated for simple websites. You'll end up in bower-npm-grunt-etc-etc hell very quickly.
Vulcanize is pretty cool, though we had a hard time getting it to work right in a gulp workflow.
lacks older browser support
mixing it with other virtual-dom libraries like react is not easy or straightforward.
I've got a project in the pipeline for which I was planning to use Cycle.js, but I've always had a niggling interest in Polymer.
What I'd like to know is whether Polymer offers any significant pros, because after consuming some of the docs the offer seems to be a better reimagining of ASP.NET WebForms. What are the benefits?
This post is a shining example of exactly what people want to hear when they perceive a company/organization has failed (especially when it's apparent to the company/organization). It's direct/to the point, doesn't mince words, doesn't attempt to twist it into something it isn't and instantly, in my case, raised the level of respect that I have for YC. Personally, I didn't fully understand the controversy and didn't feel it was as big of a deal as it was bubbling up to be, but everyone has their opinion. Had I been on the "yes, you fucked up badly" side, though, this would have been a response I would have never expected and been pleased to see.
I know there are reasons that organizations don't offer this level of candor. Many of them are the same reasons people choose not to apologise/own up for their own mistakes. The only valid reason is the one that comes from the legal department: Outright admitting a mistake opens one up to possible liabilities and an easy win from a plaintiff in court. In the especially litigious United States, this could be a "death blow" kind of risk. When it's not, I wouldn't want to be the guy in charge of weighing the "goodwill" benefit from handling an apology correctly against the costs of litigation (I'd prefer to attempt blind-folded archery through the wake of a 747). But I deeply wish organizations could behave more like individuals and handle an apology properly: Admit clearly you've screwed up, state the cause and corrections to prevent it in the future, and possibly provide something as a show of good faith that those actions are being followed. I found seek out and find a way to do business with companies that behaved like that.
 Which is funny to say. Frankly, I'd have expected a response like this from YC because they've tended to behave in an admirable way.
 All of which are terrible ideas and require one to only get over one's ego. Be quick to apologise and quick to forgive is my rule. Just because malice wasn't intended (which is practically always the case), doesn't mean things couldn't have been handled better and people weren't hurt just the same.
I am a happy paying subscriber to Pinboard and enjoy his writing as much as anyone here, but Pinboard can barely be considered a startup at this point in time (running since 2009), and he seems like he has not really been interested in adding much new since then (for good reason..)
The original posting stated "It will be like a lighter version of YC for idea and prototype stage companies" - Which doesn't fit Pinboard at all.
I think the original response to the voting, etc was handled very professionally by YC, and Maciej should spend more time writing and less time stewing up trouble.
1. Allow more than 2000 characters for the application description. I dont think we need to make this endless - something like 5000 characters should work.
2. Increase the contrast of the text in the description - as a (slightly) older person reading large blocks of light grey text on a light grey background is hard going.
3. Set clear guidelines on what we are supposed to be judging the applications on. Is it what we would most like to see funded, or is it what we think is the best fit for YC?
4. Once a shortlist is selected then let the applicants update the description in light of the discussion they have had. In my case I learned from the questions asked that many people missed what the market was for my idea and dismissed it on that basis. I really needed to go back into the original application and update the description to make this clearer.
5. YC should not limit themselves to the winners of the process. If they see an application they think is a great fit for YC then just interview the applicants. YC is getting a different category of applicants in both cases. In my case I put in an Apply HN application yet I had no interest in applying for a standard YCF or the YC program. Edit. I should add here that I am probably not a good fit for YC, but I am sure some of the other applicants that did not win were.
6. We need some better way of deciding on what is more important - what appeals to the HN community, or what has wider appeal. The HN community is a great resource, but it is not necessarily the best market for a startup. Many of the applications were voted up on what HNers wanted, not on what we thought the wider world wants.
If anyone wants to join me in also donating to the San Francisco Coalition on Homelessness, here is the donation form linked on their site:
(You have to actually click the "Take Action" link in the header: http://www.cohsf.org/)
There's a fine line between "wisdom of the crowds" and "American Idol for startups". I'm not sure exactly where Apply HN falls. It doesn't seem like any individual investment will make or break YC, and this is an interesting idea for an experiment. But I don't come away from this feeling upbeat about the democratic process.
In the world of PR, there's a very strong bias towards appeasement. If a controversy gets big enough companies tend to just 'give in.' But these victories are hollow ones as the true rightness or wrongness of the controversial actions become irrelevant. It's impossible to know whether a corporate/organizational apology is genuine or if the stakeholders are simply appeasing the crowd.
My gut says this phenomenon has become more powerful in the social media era as consumer voices are more easily amplified.
Fuck-ups happen. The biggest difference is how you deal with it.
It's very hard to do this, and it's my firm belief that only those of good character have the strength and fortitude to do so!
Maciej, you're a gracious guy and the manner in which you handled this was also exemplary.
As an aside: dang has one of the toughest and most thankless jobs you can imagine: moderating HN and ensuring that trolls, unstable people and those with hurt feelings are fairly dealt with and at times corrected. I am one of those people who dang has had to quietly speak with after I emailed HN, and his gracious, open and firm communication speaks volumes, and is one of the reasons why HN is the best and most interesting forums on the Internet.
* Say that the HN community will select 2 project for an interview for the YCF program, so it's completely clear that YC has the final word, veto power and whatever additional conditions seam necessary.
* Keep the last vote open for at least 24 hours, as it was in the extended period. I live Argentina, so I have a an hour similar to USA, but it would be nice that the people outside north/south America have time to vote.
* (More difficult) Enable a "hide" option for the ApplyHN threads. There were more than +250 applications and some of them were good and some of them were "obviously" bad. I'd like to filter them from the random order (without flagging them), so I can make my own shortlist of 30-50 applications to read them more carefully and upvote a few more.
1. Make this "HN selects startups which get invited for YC interviews", i.e., a feeder into the existing system. Essentially, use HN to supplement the network of YC alumni who help out with the application-filtering.
2. Since YC will explicitly still have the final say, open this to both Fellowships and YC Core applications.
3. Have a standardized form. Or possibly even a "make this application public" checkbox on the regular YC application form.
4. Use a more sophisticated voting system. I think a "which of these two looks better" combined with a form of Elo rating could work quite well.
EDIT: To the people voting this comment up: Do you agree with all four of those suggestions, just some of them, or are you voting it up because you like the fact that I'm offering ideas despite thinking that these four are all bad ones? As Dan has said a few times recently, discussion is more useful than votes. :-)
@dang - I know you sometimes have to make tough decisions where all parties involved end up unhappy with the end result. But I'm sure that the vast majority of the community appreciates what you do. At the very least I do.
It's not said very often, so I wanted to rectify that.
But I have to say it's pretty cool to see this response. Shouldering responsibility and admitting fault is something that most people avoid and most businesses don't even think about.
Dang and YC have done well and played their part. Maciej has not.
I am with @nickpsecurity in stating that Maciej is misappropriating the money invested in his company. Of course the argument can be made that
1. The money did not get to him at all.
2. Too much bad blood has made participation untenable.
Irrespective of the above, the spirit and intention of those that voted him (I did not) and those that insisted he be given the money (I did) for for Maciej & Pinboard to participate in YC so we can see what happens and how it will affect the product. .
If we are looking for who YC should make charitable donations to, we would mention that.
The aim of this scheme by YC was to engage and bring the community together and it has brought a lot to awkwardness. This is mainly on Maciej and doesn't look good.
To Dang and co, keep up the experiments. Not everyone will turn out as planned.
You are both awesome people who are genuinely interested in doing something different to help give new ideas a nudge forward. It sucks that this blew up, but I think the original intent still rings true and I thank you both for giving us a chance to be a part of it.
Alternately, what Maciej did with the money is more irritating now given point of competition and his comments in it. I was more interested to see what value in business he could create with it given Pinboard success. (rolls eyes)
Rules would be that you couldn't have any equity in said company or have ever received any compensation from them.
Could the HN community vet them as well as you do?
My suggestion: Next time ask a private application for YCF with the sole purpose of considering an application eligible on whatever (transparent) criteria you choose. And dont take it lightly. Be 100% sure that you would give the 20k and mentoring to any of the eligible applicants.
Then create detailed rules and guidelines that allow removing an elegible applicant from the poll and publish it.
Then, only then, publish the poll and state that the 2 most upvoted will be selected.
This is really crap content, please cut it out
- give a 2 week window for applications to go up. Only publish the posts all at once, once the window shuts
- give every user one vote and one vote only so there is a cost to the user in voting
How about publishing rules for a contest and sticking to them, or canceling the contest entirely if it's not going the way you expected or desired? If there was a risk that some founder you didn't like would be picked the rules should have been clear about how to prevent that (through interview, etc.). And if you realize the rules didn't cover this contingency then scrap it entirely and start over with new rules.
Frankly I'm surprised that this is being pushed back as some failing of the HN community. This is clearly a failing of the contest creators.
Don't open up a selection process if you're not going to accept results that aren't already of the sort that your insider selection process would have picked anyway.
In another thread you called Pinboard your "Boaty McBoatface scenario." The thing worth understanding is that Boaty was the best possible outcome of that poll. If they had wanted to keep to status quo of boring and vaguely-majestic names they should have never opened the process up. Boaty was not a failure, Mountain Dew's poll that selected "Hitler did nothing wrong" was.
Unless you're ready to paint the giant cartoon eyes on the bow of your ship, you don't actually want outsider ideas. So why are you asking for them?
The things that was different about him was called out as faults (participating on his own terms, not knowing rules, making you uncomfortable), he was forced into the normal interview process (which you both said wouldn't happen and explicitly tried to attract people who wouldn't want to, then using that as an excuse to reject him), the "be nice" rules wasn't enforced on the many comments attacking his character as a result of this process and bias wasn't avoided.
It's one thing to change the rules, another not to be true to the premise of the experiment. How could someone now in good faith recommend a YC initiative to someone who doesn't fit the mould, when you can't even make it work with "one of your own"?
 "Hacker News users have many diverse perspectives on technology and business. Perhaps if HN picked startups, it would pick differently than YC. Maybe different startups would be motivated to apply, if they knew that the interviewing and deciding would be done by the HN community." https://news.ycombinator.com/item?id=11440627
 "Anybody who applies to HN in public this way is putting both themselves and their baby in a super vulnerable position. We're going to rise to the occasion by being not only civil, but nice." https://news.ycombinator.com/item?id=11440627
 "Its easy to form some really bad habits when you sit in a position of power to judge the potential of a person, a team, an idea and their executionbelieving that you know better and focusing your time on finding weakness." https://news.ycombinator.com/item?id=11440843
Democracy has to be more than 2 wolves and sheep deciding what's for dinner.
> If any of you have suggestions for how to do better, I'd like to hear them.
Y Combinator needs an impartial, independent ombudsman dedicated to tackling implicit and explicit bias both within the YC application process and, especially, on Hacker News itself.
As the interest rate fell from 14% in 1981, to roughly 0% today, and mortgage rates fell from ~20% to ~4%, people could afford to pay more and more, comfortably or otherwise, for their homes, and because often people buy the biggest house they can afford as a proportion of their monthly income, the maximum people can pay will continue to rise as interest rates fall. This drives house prices upwards.
As house prices rise upwards, all homeowners will have increased equity-debt ratios, giving them additional collateral to further pledge their houses to increase the amount they can borrow to spend on more properties. It is a pro-cyclical effect on house prices.
Even the current average tech worker wage at good companies will make buying a home on your own fairly impossible. Forget buying if you are someone who works a normal type job.
A house selling for 250k in a decent neighborhood in 2000 has jumped to 850k in 2016.
You can only raise prices if you can find buyers who are willing to pay. If you used this pricing model as a real estate agent you would find yourself completely unable to sell houses pretty quick if, for example, people started moving out of the area. In that scenario there would be more houses for sale than buyers, and the real estate agent with the lowest price is the one who will actually get the sale (and if youre still increasing prices that agent wont be you.. you'll be going out of business).
This is why people cant increase prices forever - you have to lower your prices if the buyer has a lot of good alternatives to buying your house.
To influence the price of housing you need to increase the number of good alternatives for buyers. You can do this by driving people out of the area (lame), or you can build tons of housing.
This is all based on one of the fundamental ideas of modern economics, the supply and demand model.
1) On average in my jurisdiction, people sell their houses once every 10 years. So the 6% Fees would account for only (6%/10 = 0.6%) annual growth, not the whole 6%.
2) You could compare this to an area where agent fees are much lower. For example, most of my real estate industry experience is in Queensland, Australia where until last year Agent Commissions were capped at 2.5%. If your theory were correct, we would have seen growth rates closer to 2.5%, when in reality they average about 6-8% per annum here as well.
I like your thinking though!
http://andrewchen.co/ Andrew Chen of Uberhttp://jwegan.com/ John Wegan of Pinterest
Probably more growth/product focused than PG and SA, but definitely give some excellent insight.
This will reveal the inevitability of verbal interfaces in computing devices (esp. mobile) and the difficulties therein.
It's then worth extending the effort another step, to introduce yourself to the statistical and numerical techniques used by natural language processing pros to keep up with the explosion in language in modern media: personal, social, and mass.
Wasn't my cup of tea but at least I know what it is like on the dark side.
Only danger is after doing it for a year it was harder to ace the technical questions at interviews.
Its one of the few books I keep buying and giving away.
1. Use your application. (Not the same as testing.)
2. Adopt an apprentice programmer, teach them your seat, pass on the seat. Leave the seat.
3. Program something for fun that is your own idea.
4. Program something for someone else that is their idea.
5. Sort the books/library.
6. No books/library? Build books/library.
7. Re-write the code from scratch, for the hell of it.
8. Take over someone elses' project, finish it to the end users satisfaction.
9. Give your project to someone else, in a state that they can do #8 easily.
10. Build a list of positive observations over a period of X, where X is how long you think it might be fun to do so.
The accomplishment of a number of these actions have, in my opinion, resulted in some really great programmers and some really great software.
Here's what I suggest.
(1) If you can financially afford to quit, quit. Take a couple weeks to sleep. Then start looking for a new job. Your experience is extremely valuable and if you are in any major metro area you should find one in a month or two.
If you can't do this:
(1) Call in sick for a couple days to a week. Get some sleep, do whatever fun activities make you happy.(2) Start interviewing for different jobs. Consider using tools like Hired or Indeed Prime where you can get lots of opportunities in a short amount of time.(3) As soon as you get an offer that is better than what you're doing now, give notice and start searching full-time for a new position.
You only neded to know which HTML tags worked on IE and Netscape. We did our layout with tables... And they worked.. 100% of the time.
Latter came CSS, and for the next 5 years everybody went looking for the holy grail of CSS that was a layout that looked like tables did.
The the browser wars ended, IE won and maybe could have some peace... But it didn't last.
Then the iphone came a long and now, your webpage gad to work in a screen resolution you didn't know existed.---My conclusion:Front end development is an inestable mess.
Plagued with accidental complexity as defined by Fred Brooks.I left it around the time I realized that fighting CSS layouts to do what a table could wasn't for me. And I stayed as a back end developer.
I definitely recommend changing direction but not completely, where can your skills for usability and design be valuable with less of the accidental complexity??
Maybe mobile development?Specialize in a single platform and become an expert there?
I'm the inverse of you! I got inspires to say this, like that guy who said he created the inverse of angry birds.
Ten years ago I was in those boring computer science courses constantly falling asleep, being told that many will not make it to graduation, and seeing with my eyes burnt out students in last year of study. Slowly my decision was set, I dropped out and have studied whatever I wanted to know about for all these years. You can bet I know a lot about the world. But I only started to learn developing few years ago, and I'm much left behind compared to those who worked continuously. I tried to start over in a different careers many times in those years, and believe me, its harder. You need a break, to recover, maybe you lack knowledge about how the world works, or what the true face of employers is, but its cheaper to pay money to find that than to start all over.
Be aware of working in teams, maybe you dont know what collectivism is, you might think communism as a name of the past, but it could be reincarnated into another leftist ideology.
Take a break, you are ahead of many, and dont waste your savings.
Redwood City is easy to reach, there's a caltrain stop right next to where the fair is taking place.
Without knowing what your skills are, it's hard to make suggestions. But ... have you looked at working at a top notch company where your skills would be very much in demand. For example, with the right skills you could land a very well paying job in banking in say Frankfurt or Zurich. I've worked for a Zurich insurance company and that was one of the best paid gigs I've ever had.
What skills do you want to be using?
This way youtube will suck your bandwidth and resources to force-run dozens to hundreds videos through your computer and internet connection.
This will allow Youtube to inflate actual view count numbers and defraud both the publishers and the advertisers.
Do the advertisers really think this behavior makes me want to buy their product?
If they can erode some of Snapchats market share with their upcoming Snapchat-like app then they will be doing well.
What is really enlightening though is implementing a basic one, because it is so simple. The core of it involves popping two graph nodes from a heap and pushing a new one. I did this in school, and was impressed by it, but became far more appreciative when I tried to do the JPEG way. It doesn't even provide a table, just a histogram!
It also acted as the basis for the successor of arithmetic coding, which is pretty much in every modern video codec. Can you imagine a world that is still analog because we couldn't figure out how to transmit digit video or images or audio? Huffman is a key link in the chain between the past and present.
Another interesting but asymptotically slower integer/polynomial multiplication algorithm is Karatsuba's.
While we're on the subject: This book is a great read: http://www.amazon.com/Nine-Algorithms-That-Changed-Future/dp...
RMQ with linear preprocessing and constant time queries (which is also true for multi-dimensional cases, if the dimension is bounded by a constant).
Knuth-Morris-Pratt pattern matching is the first algorithm where I saw the usage of an additional variable in the pseudocode just to simplify the complexity analysis.
If you want to be a teacher or hold a research or Engineering position at a more research driven corporation, and get a confortable life and safe career, get a PhD.
If you want to work your ass off for +10 years at least, life a insecure and stressed out life, have 0,1% chance of being insanely sucessful, rich and change the world, do a Startup.
Doing a startup trying to achieve only "career recognition" or improve your resume so you can land a job at Google or Microsoft is a total waste of time. You'll likely fail, lose your money (and your investors', if you get any) and achive nothing. Being a sucesfull entrepreneur would definitely make your resume better, but that's not the end goal.
When you see startups being acquired by Google you shouldn't think the founders reached their goal. Quite the opposite. It's usually a mild failure (an "acquihire" or "softlanding"), they couldn't scale their company or raise more money and selling to Google was the best thing they could do (besides shuting down the business). Or it was a mild success, the entrepreneurs sold to Google because they would get some sizeable amount of money fast enough, rather than taking the risk to see if the company would become much larger down the road, to sell or IPO at a much higher valuation 5 or 10 years later, for instance.
In either cases the founders won't usually be happy to have become employees once more, and will leave the acquirer as soon as they can and do something else. They can't leave right after the acquisition because he will be vested or will have golden handcuffs (ie.: won't get all his money if he leaves before 2 or 3 years).
Ps.: I have a startup (for 6 years now) and before that I was studying to get a Master's Degree. However, my A plan was always to start a company even once I started the program. So once I got some money to start, I dropped out. I was already quite tired of the academic life and don't regret it. Don't regret the time I've spent doing the master's also, as it was a way to keep myself ocuppied and get some ramen money, while having a lot of free time to work on my product and think.
When considering a PhD, the best thing to do is look at the advisor(s) you'd be working for and their repertoire of projects. Looking at the "discipline" isn't precise enough; there's a wide range of stuff happening within fields like information systems or computer science, everything from very theoretical to very practical.
Where I can't use Tamsyn I use https://github.com/rbanffy/3270font
I like fonts that are easily readable when small so I can get more screen realestate, and bitmaps are the best for that, but 3270 is pretty good as well.
--asterisk=height --i=serifs_round --l=serifs_round --zero=slash --lineHeight=1.4
Since then using:(paid)https://cloudcraft.co/https://textografo.com/
I usually stick with what I know, such as powerpoint, but I have a difficult time making it look professional.
I love the README files in markdown in any git repository that are pretty descriptive on what their architectures are.
As far as the most respected bootcamps, based on who I've talked to I would say App Academy, Hack Reactor.
However, I would only recommend HackReactor and App Academy in San Francisco as those are the bootcamps I've seen grads consistently do well in.
I find that the placement stats are a bit bs at bootcamps since they are unaudited but I have a strong confidence based on my network that both Hack Reactor and App Academy place 75% of their grads within 6 months into 6 figure jobs.
Happy to answer any questions.
Also worked with a HackReactor grad who did some good work on web and embedded stuff (which he learned on the job). One of the common traits of these bootcamp grads is that they were willing to build stuff and took time to learn (ask a lot of questions).
I think DBC also has hiring coaches and a good community for career help. Also, I think DBC alums often go back and mentor new developers in the program, which is nice.
my ex-company hired 1 junior engineer from hack reactor and she has since then gone on and accomplished good things at other companies. And 2 of my ex coworkers transitioned into dev roles after going through hack reactor as well. They have all had positive experiences.
I have also heard good things about hackbrite if you are eligible. One of my ex-coworkers is an now instructor there and she cares passionately about cs education.
Source: I used to work in edtech in the valley so I have relationships or heard 1st hand accounts about these boot camps.
If you're looking for a job, I'd want to know way more than percentages. Companies, positions, salaries, etc.
I do recruiting and have seen a number of boot camp grads, and their first job is usually an (unpaid?) internship. Boot camps are at most 6 months of study (often compressed to 3). That's not a lot, compared to BS or MS in CS. You may want to look at remote masters programs, like Georgia Tech's.
Using the name of a boot camp as the basis for judging the abilities of a student is a fool's errand.
Recruiters who do this are making a serious mistake. I say this as somebody who has interacted with hundreds of boot camp graduates across multiple boot camps. There is such a wide range of abilities that move through every boot camp that you really cannot generalize about the talents of each student.
I don't know whether to blame it on the influx of money into the space, the death of RSS, or the ever shrinking number of people who understand the details of modern RCE but finding quality content with any regularity has been extremely hard to come by.
Blogs are usually mentally taxing and very technical. At least with talks we get the person's own voice which is much more preferable to text, as there are subtleties in the langauge that are usually left out from blogposts
thegrugq (his medium and tumblr)
and slides/videos from sec conferences are always great.
As to the question, how about OTR+XMPP or Signal. Signal desktop is in beta. I don't think you need to worry about running the desktop Chrome extension on iOS since there's a native iOS app too?
More seriously, is there a reason for native? Just it's a fairly arbitrary request without more detail, since a network connection is needed anyway. eg. WhatsApp web client is good enough that it 'feels' native.
Just do what I do: click on their name, find a recent comment of theirs, and reply with a message to contact you via your profile email (or whatever) for a solution to previous problem. It's how I got a hold of at least one person here in same circumstance. A few others are on list when I get time for their more difficult areas of expertise.
I think one of the reasons it's not quit so actively developed is the philosophy behind the project which has a lot to do with PG. He thinks people care about content, not features.
Another reason is that it's written in arc. It's hard to find lisp hackers, let alone arc hackers: http://arclanguage.org/forum
Currently, everything on HN is public, except for password (hashes), emails, and who [voted for|flagged|vouched] what. If all HN user data leaked right now, it would be a bummer, but not very scandalous.
We didn't want to be trusted with private communication. We're not perfect, and it's easier not to leak data you don't have =P
* HN Alerts will send you an email whenever someone replies to one of your comments: http://www.hnreplies.com
* HN Watcher, monitors HN posts for keywords, or you can follow certain users & have their comments & submissions emailed to you: http://hnwatcher.com/
I don't want yet another inbox I have to check (ie HN private messages!), but listing contact details in my profile & having alerts sent to my email has been really useful to me.
Not saying it couldn't be done right, but it might be involved and go against the HN minimalist philosphy.
Junho I dont think we have every personally talked but I believe my company has worked with you in the past.
I'm not sure if you know Griffin at Enova but he started the Chicago CTO Forum over three years ago. I think its exactly what you're looking for. I've personally worked with or represented half the guys in the group and they're all great. It's probably the most impressive collection of VP/C level guys in Chicago.
You probably know a couple of them but if not let me know and I can intro you.
Wanna connect via email and make this happen (email@example.com)
-Programming Principles and Practice using C++ 2nd edition (by Bjarne Stroustrup). This covers everything, although is a bit dry at times.
-Effective C++ (by Scott Meyers). A bit "outdated" from a language standpoint, but many of the techniques still apply and also, not every C++ codebase is using the latest and greatest anyway.
-Effective Modern C++ (by Scott Meyers). A new set of "best practices" for a more modern C++ environment
I haven't found many good resources for JUCE other than reading through the JUCE forums, the project doc (often lacking), and reading examples. What is often helpful is to first understand C++ a bit, then learn the audio specific code and underlying DSP principles in a C++ context. Then it shouldn't be too hard to transition to JUCE on your own. The best books I know for this are:
-Designing Software Synthesizer Plug-Ins in C++ (by Will Pirkle)
-Designing Audio Effect Plug-Ins in C++ (again by Will Pirkle)
What I really miss is some kind of partner to learn together with, that would be awesome and we could have a lot of good discussions.
If you were just starting out, I'd suggest you work with Xamarin to do your app development in, and Unity3d if you were doing games or 3d work (Though you could use monogame with xamarin if you were so inclined). But then again, my comfort zone is C#.
Android and iOS apps these days tend to look very similar, with the main difference being a soft back button for iOS and none for Android. Windows phone can look very different if you use the Metro design language but quite a few apps that I've used seem to be mostly ignoring it (admittedly niche ones) and looking like the big two.
Whatever developer you hire will be "better" (or at least more comfortable) at one platform than another.
Have you done your market research? Are you targeting a particular market that is likely to have one phone type rather than another? I've noticed that the different platforms tend to attract different types of people. App Annie is a good source on this market data though you'll have to ignore the most-popular apps as you're not going to be the next facebook/ebay etc no matter how hard you try.
I believe I know more people who make good, consistent money from on-the-side real-estate transactions than people who make 5-figure yearly bonuses.
I'm not sure if this counts however, as it's a case of my salary being paid out every three or four weeks (depending on the pipeline) instead of every two weeks.
I've never received a lump sum of more than 20 or maybe 30 thousand at once. I have received a five figure bonus before though.
I'm not very rich.
I think I sold a good chunk of Amazon stocks ~ 50k as well (after tax)
Can you apply for a STEM extension now? That will keep you in the country and let you work for another 24 months. Try to get the highest paying job you can and then Aggressively save to pay off your student loan?
After that to continue staying in the country you'll have to get an H1-B. Having graduated from a US masters program you have slightly better chance in the MS cap but the odds may not be in your favour.
The safest option would be to plow through your PhD program. But you probably already knew that.
Quitting the program and getting a job might be a gamble, but weighing the risks is something you'll obviously have to figure out.
> start failing my PhD program because I just can't take it anymore?
I don't know how serious of issues you're having when you say "just can't take it anymore." If it's anything like what I experienced, it's not unusual. I wanted to quit really often (once per month?) for several years. And I actually did informally quit for a few months.
Sorry that I don't really have any advice. Just relaying my thoughts on "just can't take it anymore": every PhD student feels like that at some point.
I would work on automating what you can to save yourself time. Be on the look out for easy things that can save other time and present proposals to implement X and save Y time.
I'm been in companies though where for whatever reason no one wants to change/improve anything. Some fear automating things saving time will cost them their job or they might not understand/not want to learn new things. So they are never going to be open to change.
Be on guard for things going wrong and being blamed for trying new things. Learn that they are doing inside and out, then look at ways your team can do it better.
If you just settle in and keep doing what you're doing take some time to learn new techniques and technologies that can help you later. Maybe start a blog, writing to build an audience to make you an 'expert' and open up possible product offerings in the future. (If that interests you).
Good luck, some companies are never going to do things the 'right' way. Good luck passing along some best practices.
By providing solutions. You don't sound like you're busy doing stuff all the time so you can spend the time you are waiting for a meeting just doing things. Find a few low hanging fruits where you can make life for others easier, preferably things that save them time. Over time you build a reputation and people will start to actually listen to what you say. Until then, don't talk, just do.
Log patterns and avoid premature automation, but write down the time you and others take to fix issues and then you can say that technical debt because of blank cost the company X days this last Y period.
Also work on projects that showcase you can get shit done to build up credibility. Everyone who comes in as a junior engineer with different ideas will come across as the hot shot who thinks he knows better. Reach out to the developers and ask them what are areas where automation would make their job easier. Reach out to management and ask them what they want more control over, or want done quicker through automation. Look for other costs, server costs, service costs, etc.
Your frustration likely matters to nobody but yourself though. Find their frustrations and fix both simultaneously.