sippndipp

I understand the depression. I'm a developer (professional) and I make music (ambitious hobby). Both arts heavily in a transformational process.

I'd like to challenge a few things. I rarely have a moment where an LLM provides me a creative spark. It's more that I don't forget anything from the mediocre galaxy of thoughts.

See AI as a tool.

A tool that helps you to automate repetitive cognitive work.

I've always loved the Z80 and felt home with the 68k.

Quick Questions out of curiosity: What ideas have been rejected during the design process?

Great insight for everyone who wants to design more complex UIs.

Awesome app. Love it.

Tightly integrates with my calendar. Easy, keyboard driven divide and conquer for my documents into tasks. Way better than all the other knowledge base apps.

We're doing an newsletter dedicated for Android developers:

https://androidweekly.net/

- it was four years without making any money

- with ~100k subs it's generating money

- everything grew organically

I wonder I've done almost the same writeup (a little more detailed if you want to do machine learning) - and no one cared: https://news.ycombinator.com/item?id=24197884

This one here is frontpage HN :-)

Feel free to look at my post as well:

https://9elements.com/blog/developing-a-week-on-windows-with...

I think you should give it a try. Rails made me a better software architect and showed my the importance of writing expressive elegant code. It might have lost some market share to other techs (Node / Elixir) but it's still the original.

I have found a paper about CRUSH maps so far (from the Ceph project): https://ceph.com/wp-content/uploads/2016/08/weil-crush-sc06.... but I think there is more.

I personally would never use PHP. But if you have to: Go with Laravel - it's the best Rails clone around.

In my opinion your requirements are a little fuzzy. If you're developing a website (no hard database requirements) you could go with something easy as jeykill, middleman or gatsby. If you're developing a web application I would try to evaluate my future needs:

Need #1: Since I don't know what my users will do I need to be agile and quickly adapt to business changes. Tool #1: Rails - the flexibility of RoR is still unbeatable. Especially if you're a startup this is really a timesaver. Furthermore it's no rocketscience to develop a decent frontend on top using React or Vue.

Need #2: Shitload of people will use my site. Tool #2: Elixir / Phoenix has kick ass performance and language and framework are well written and thought through.

Need #3: My whole team are frontend devs who just know JavaScript. Tool #3: Maybe Node.js is for you. In the past I've rarely seen a good Node.js backend project but if you're really disciplined (aka writing a lot of tests) it should be doable.

Need #4: My project is a FinTech and I need to talk to banks. Tool #4: Java/Scala/Clojure since you'll might talk to these services directly and all of the have JVM based SDKs.

Need #5: I'm a microsoft consultant. Tool #5: Well then go with C#/F#.

We're running http://androidweekly.net and http://swiftweekly.com?

It was roundabout 5 years just editing and making no money. Now it's making money - but just a side income.

1. Content is king! 2. Start to build a community (if you link someone in your newsletter just ping him on twitter). 3. Go to community events.

Doing ads on Facebook and Twitter actually didn't work that well.

Thanks all for the feedback.

1 hour

2 hours

3 hours

4 hours

5 hours

6 hours

7 hours

8 or more hours

There is some truth in there... Too many cargo cult devs out there: http://en.wikipedia.org/wiki/Cargo_cult_programming

But to answer your question: It depends on the business you're in and the dev culture your company established.

In the most consulting shops or early stage startups I've seen the situation that you're describing. Cranking out code because visible features / products is the only thing a customer cares about.

But in companies that build a sustainable product that needs to scale things are different. They embrace good architecture TDD/BDD. They embrace time for refactoring. Maybe you should switch your job :-)

What an awesome idea to use gopherjs. Just added it to http://golangtoolbox.com/ - if you have more tools that are great please add them here.

I get your point - but I wanted the article to be more about our experience with Go rather than pros and cons of GC :-P

You should test your sites with these two tools:

http://www.shellshocktest.com/

and

http://shellshock.brandonpotter.com/

There is a well maintained guide at Digital Ocean that explains the nitty gritty details:

https://www.digitalocean.com/community/tutorials/how-to-prot...

If a server is vulnerable there is a great guide that helps you to deal even with old systems:

https://dmsimard.com/2014/09/25/the-bash-cve-2014-6271-shell...

Why not using a name+androidweekly@domain.com tag? Gmail and many providers understand it. PS: We will not send you shit :-)

I always had trouble with their hardware. Random crashes and they needed two repairs until they changed it. Mavericks seems to be very buggy and I have to consolidate my whole dev environment again. Would like to switch to a real Linux (Ubuntu / Debian). I don't want the Retina stuff since for such a high resolution the devices are underpowered.

They look really powerful. What OS do you run on it?

No

Yes