jim_d

I was worried about this as well and found a nice product called CharGon that I've been using since last May, no bristles and it makes short work of cleaning the grill:

https://www.amazon.com/CharGon-PATENTED-PERFORMANCE-CLEANING...

I am not affiliated with the company at all, just like the product and know it's safe

I think it's even worse than that, I suspect there have been a lot of companies like CA that have had their access cut off and have retained the data. FB probably has never done a serious investigation of most of them.

This one is only important because it's gotten so much media attention. If it wasn't related to the election it would have been business as usual and nobody would care or know about CA.

Agreed, I always double check that the browser password manager works, but it's tricky because there is no standard around what the fields should be called to make it always work. The best way to make sure it works is to put the username directly above the password in the same form, that will result in most password managers working, and this is especially important on registration forms.

Also for those that don't know why hunter2 was used above, enjoy! http://i0.kym-cdn.com/photos/images/original/001/065/965/989...

Great list. I've bookmarked this and already identified many interesting articles to read, in particular your articles on sales should be helpful as that is where I have the least experience.

happy to see MariaDB getting some investment, hoping it will continue growing.

This made me smile. Good work.

ps: a nice big demo button beside 'View on Github' and 'Release Notes' would be a nice tweak :)

what marketing did you try and what did you find really worked?

I've got a side project that I'll hopefully be launching this month and I would love some tips.

This was definitely fun to try.

It makes sense to me that larger projects would use forums, just to make sure you don't pollute issues too heavily.

TBH when I do interact with projects on github I'm mostly interacting with smaller projects and maybe issues are 'good enough' there.

For the larger projects they tend to have better documentation or I can have questions answered on stack overflow, maybe that's why I haven't run into this yet.

I'm wondering if you would have success trying to target projects that are growing rapidly or are in a mid range of popularity. Ideally the product is also giving back to the github repo authors, maybe it's automatically creating an FAQ for them?

I hope some of this helps :)

BE: Scala/akka http FE: Scala.js, SASS, no bootstrap

This is a really excellent article about making and launching things. In particular the notes on how you changed your messaging for different communities is excellent.

my 2 cents.

github issues seems to be where most interaction with the community happens. It might be a bit of abuse for their intended purposes but every time I've had a question a github issue usually gets an answer pretty quickly.

What use cases does the forum service fullfil that github issues isn't a 'good enough' solution for?

A quick look at the documentation and it seems like this might hit a sweet spot in replacing Make, is that the intended goal?

Also what other builtins are planned?

what types of features do you think would make it more useful for this use case?

This is a great list, thanks for putting this together. As a small feature request it would be great if I could see more of the apps at once, I think infinite scroll or just more apps per page would be nice.

I just wanted to take this opportunity to thank you and the team at Lightbend. There is a clarity of thinking and expressiveness in Scala that I haven't found in other languages. I have used Scala professionally for the past 3 years and enjoy it immensely as a language.

completely agree. There is a certain beauty to the first version that once you've learned the concepts it seems a shame to have to write the second one.

I haven't tried Go myself and I've been meaning to, but I have spent the last 3 years writing Scala code. Before learning Scala I didn't have any real experience with FP, and I think that was the real learning hurdle for me. Once I learned the FP ideas Scala became my preferred language. I think it's really funny but Java and C# have been becoming more Scala like, and to some extent the latest version of JavaScript are also starting to become Scala like. What I have come to accept is that Scala does take people time to learn, but it's not typically Scala the language, it's the FP aspects of it that are the stumbling blocks.

PS. I also work on a 100k Scala program and can go from clean to compiled in less than 2 minutes, and incremental compiles are extremely fast.

As a recent new father having my mother and father in law has been extremely helpful. For my wife and I we made a decision to move from NYC to live in the same city as them to start our family and that decision has made our lives much easier.

Where I sit with the entire thing is that this is a stark lesson in why security is important, and how effective phishing scams are.

However, once that information is out there, and verifiable through means like DKIM, we should absolutely scrutinize its content, and every voter should follow reports closely.

I've been using Scala professionally for the last few years and really love it. I've also been doing a lot of JS work professionally, so I think I'm going to really dig into Scala.js.

This was my thought as well. Then I started thinking about the huge amount of moderation effort to make sure that comment sections stay civil. From where I stand it seems like for most writers offering a comment section is a lot of work for a very small payoff.

Hi Alex,

Great work. I'm curious how did you get your affiliate programs in place, did you reach out to folks or did they reach out to you?

Thanks for working on such a great idea. I know that Firebug has saved me enormous amounts of time, and it was a big part of my tool chain for a long time.

I'm curious what people think about type checkers in JS. I've been doing full stack development for the last few years and BE development before that. Type safety has always been worth it to me, we adopted Flow and haven't looked back, although some FE developers aren't big fans of it.

I think the interesting thing is that for 90% of what is being built most tools are overkill and JQuery is really good enough. I say that as someone that started using React/Flux almost 2 years ago, and as someone in the midst of moving from Flux stores to Redux. The power of these tools is when there are large teams involved, when the complexity of the state on the FrontEnd is extremely high, and when you absolutely need a Single Page Application. Most of the time all 3 of those conditions aren't true, and in those cases you're better off using something like jQuery which is boring, easy to reason about, and everybody already knows it well.

This seems strange to me as well. How were they planning/tracking the work that needed to be done for their project?

I've found that code reviews are one of the best ways to increase code quality. Even just talking with other developers about why they've done things is helpful in thinking about simpler options and keeping things closer to the architectural vision.

You'll likely have the easiest time looking at an industry you've already worked in. Your years of 'X' experience in a given industry means you'll know all the jargon and have a leg up on the competition. Good luck with the job hunt.

Facebook as news curators already didn't work very well (http://gizmodo.com/former-facebook-workers-we-routinely-supp...), here they're going to be fact checking and we'll have to wait and see how well they manage that. Most writers use real facts to create incorrect narratives, and if they're only reviewing what is factual that still leaves a lot of room for interpretation.