On the Laravel News site, they've posted the announcement of the release of the results from their 2018 edition of the Laravel Survey.

We partner with LaraJobs to run an annual Laravel survey to see what types of projects people are taking on with Laravel as well as get some feedback on what the Laravel community could be doing better. The results ended up with over 1,500 submissions, and some interesting insights.

You can see the complete results on this 2018 Laravel Survey Results page and thanks for everyone who took the time to fill it out.

Questions asked in this year's survey included topics such as why they selected Laravel, size of projects, if they're able to find the developers they need and what they'd like to see more of in the Larvel community (tutorials, articles, regional conferences, etc).

If you're a reader of php[architect] magazine or even just want to have an influence on what the future of the magazine might look like, you should contribute your thoughts to their 2018 audience survey.

Our 2018 audience survey is online to help gauge how we can provide what you need to be a better developers. Whether you subscribe to the magazine, listen to the podcast, or just visit phparch.com, I want to here from you. I’m no fan of long surveys so I’ve kept it short and to the point. It should take about 10 to 15 minutes at most to complete.

The questions on the survey differ slightly for subscribers versus non-subscribers. There's questions about:

• why you subscribe/don't subscribe
• if you know what a subscription comes with
• preferred distribution method (PDF, print, ePub, etc)
• their php[podcast]

There's also some questions for general demographics around your job, technologies commonly used and preferred devices. Help php[architect] magazine keep providing the content that PHP developers need and can help them enhance their careers - follow out the survey today!

The Laravel News site has a new post today sharing the results of the 2017 Laravel survey posted a while back. The survey asked the Laravel (and non-Laravel) community about the framework, what they like about it and what they'd like to see in the future.

Back in September, we partnered with LaraJobs to run a Laravel survey to see what types of projects people are taking on with Laravel as well as get some feedback on what the Laravel community could be doing better. The results ended up with over 2,700 submissions and some interesting insights.

You can see the complete results on this 2017 Laravel Survey Results page and thanks for everyone who took the time to fill it out.

The results include answers to questions like:

• why Laravel was selected over others
• what size projects it was being used for
• if you were able to find the Laravel developers needed (and of the right quality)
• size of the business using the framework

Check out the full results for answers to these and other questions from the survey.

The Laravel News podcast, hosted by Jacob Bennett and Michael Dyrynda, has released their latest episode - Episode #46: Laravel 5.5 releases, dynamic templates, and community surveys

In episode 46 of the Laravel News Podcast, Jake and Michael discuss several new Laravel 5.5 minor releases, dynamic templates, and community surveys.

You can read the full episode transcript which includes time markers and links.

Other topics mentioned in this show include the site Servers for Hackers, the release of Sublime Text 3 and the posting of the Laravel EU 2017 talks over on YouTube. You can listen to this latest episode either using the in-page audio player or by subscribing to their feed to get the latest.

On the SitePoint PHP blog there's a new post from author Shahroze Nawaz that shares the results of a survey performed with several "prominent PHP community members" about their usual development workflows.

Workflow refers to both the process and the tools that are used in this process. Almost every developer comes up with a process of creating and finalizing the project deliverables. This process is implemented through a set of tools that the developer comes up with through trial and error. Once a workflow has been perfected, developers follow the process almost religiously because of a simple reason: following workflows reduces most of the management problems that developers have to face during a project.

[...] Here are some of the PHP ecosystem’s most popular developers and designers, and their tools and/or workflows. Note that these workflows will by no means be comprehensive, but even mentions of tools used by some of the more prominent members of our community should be enough to warrant checking them out.

PHP community members on the list include:

• Taylor Otwell
• Phil Sturgeon
• Nicolas Grekas
• Manuel Lemos
• Josh Lockhart
• Cal Evans
• Kat Zien
• Laura Elizabeth

Each person on the list describes their tools of choice for both development related tasks and how they keep organized. There's plenty of links to these tools and services too for you to check them out on your own.

Each year the StackOverflow site posts a survey for developers to record their current feelings, thoughts and background. They've posted the results for this year's survey with the results from over 64,000 developers worldwide.

Each year since 2011, Stack Overflow has asked developers about their favorite technologies, coding habits, and work preferences, as well as how they learn, share, and level up. This year represents the largest group of respondents in our history: 64,000 developers took our annual survey in January.

As the world’s largest and most trusted community of software developers, we run this survey and share these results to improve developers’ lives: We want to empower developers by providing them with rich information about themselves, their industry, and their peers. And we want to use this information to educate employers about who developers are and what they need.

They start by share some high level points they learned from this year's results. The remainder of the post is the results presented in a more easily consumable graph/chart form. You can, of course, download the data yourself if you're interested in running reports of your own.

The Laravel News site has published the results from their latest survey of the Laravel ecosystem and feedback directly from developers using it (and other) technologies.

Back in September, we partnered with LaraJobs to run a Laravel survey to see what types of projects people are taking on with Laravel as well as get some feedback on what the Laravel community could be doing better. The results ended up with over 1,600 submissions and some interesting insights.

You can see the complete results on this 2016 Laravel Survey Results page and thanks for everyone who took the time to fill it out.

Questions answered in the survey results include:

• What's the one reason why you selected Laravel over other frameworks?
• How many production applications do you have using Laravel?
• How many users does your largest Laravel based SaaS have?
• Are you able to find the quantity and quality of Laravel developers you need?

For each question they've shared the results (bar charts) and provided a brief commentary along with a list of things people suggested as additions to the Laravel framework.

On the Laravel News site there's a new post talking about a survey that's being put out by the LaraJobs site/service with questions covering the current state of the Laravel community.

The Laravel community is growing fast and we thought it’d be interesting to see what types of projects people are taking on with Laravel as well as get some feedback on what the Laravel community could be doing better.

If you’re a Laravel developer or in charge of a Laravel team and have a few minutes we’d love for you to take the survey.

The survey will run for a few weeks and at the end, the results will be tabulated, analyzed and shared on the Laravel News site. Even if you're not a Laravel user, you might want to take this poll (don't worry, it's anonymous) and share some about why you don't use the framework - there's a few questions about that too.

The /Dev/Hell podcast, hosted by PHP community members Chris Hartjes and Ed Finkler, has posted their latest episode: Episode 75: Together but Alone.

We’re three-quarters of the way through to The End! In this episode it was just Ed and Chris talking about two issues that are very important to them. We go over the early results from Ed’s Open Sourcing Mental Illness survey and then have a very long discussion about the events surrounding LambdaConf 2016.

You can listen to this latest episode either through the in-page audio player or by downloading the mp3 of the show directly and listening at your leisure. If you enjoy the show, be sure to subscribe to their feed and follow them on Twitter to get the latest episode announcements.

Each year the StackOverflow site asks the developers that use its services to participate in a survey with a wide range of questions. They've just posted the results of their latest round - the 2016 edition.

This year, over fifty thousand developers shared where they work, what they build, and who they are. You are about to read the results of the most comprehensive developer survey ever conducted. We asked them 45 questions. Key highlights include the following:

For the first time, more developers are using Mac than Linux as their primary OS. Only 7% of developers identify as "rockstars". Most developers prefer dogs to cats. (But not developers in Germany.)

The results of the survey are broken up into several main sections, each with their own statistics (and graphs for some) showing the results:

• Developer Profile (including Geography, Age, Experience and Education)
• Technology (includes Most Loved/Dreaded/Wanted, Top Paying Tech and Development Environments)
• Work (including Job Priorities, Salary, Teams and Remote/In-office)
• Community (Visit Frequency, Motivation and Asking/Answering)

You can check out the details these results in the full page output.