Where programmers share ideas and help each other grow. All developers are welcome to submit stories, tutorials, questions, or anything worth discussing. The front page is curated by the folks behind @ThePracticalDev.
Have fun and don't be afraid to contribute, everyone's perspective is valuable! ✌️
I still do most of my reading through RSS feeds, call me old fashioned.
When I encounter an AMP page, there's just something that feels off about them. That they show differently in search results cheapens the content to a degree. Not to mention the lack of publisher-owned branding. Recognizable type faces, colors, and logos are the strongest indicators of the reliability of the author/content, and you lose a lot of that.
Here's a video from an event I went to last year where Calvin French-Owen, the co-founder of Segment, gives a good primer on AMP pages. It's pretty clear why they exist, but a common refrain is to just make your own site not suck. heavybit.com/library/blog/get-ampd...
At Lunar Logic we do 3 month long, paid internships. Two, soon-to-be, developers work together on a project. The internships projects are non-commercial but always something useful like our open source Rails Girls submissions app. We try to make the working environment as close to a real project as we can. This means that interns work with lead developer (their mentor), testers, designers and also a client - usually someone from the office that will use the app.
The internships have proved to be a great way to invest in new people and build their experience. Given autonomy and authority, interns very quickly become a valuable part of our team. Eventually rocking in commercial projects and also contributing to our culture.
The interesting part is that starting from day 1 interns can make any decision the CEO can make and that's true for anyone in the company. Of course, deciding on complex matters requires knowledge about company interns don't yet have. It’s not uncommon for interns to buy books they need or make pivotal changes on the project they are working on.
The pattern looks similar not only for developers but also for testers, designers and product owners.