Developers love arguing about tools. Less often heard: what they're actually using, what they're excited about learning, and what they've quietly dropped. A survey of 25 developers and 5 technology leaders at bol.com provides that data, and some of it surprises.
The survey asked three questions: what technologies are you eager to learn, what technologies did you use this year that others should learn, and what did you move away from. The answers reveal a gap between community hype and actual team practice.
Where the Hype Meets Reality
Testing frameworks show up prominently in responses — despite the common assumption that senior developers write code that doesn't need testing. That assumption doesn't survive contact with real production systems. Multiple respondents highlighted testing tools as important, including frameworks for unit testing, integration testing, and behavior-driven development.
Application frameworks generated strong opinions, with arguments for keeping code minimal and using interfaces rather than writing repetitive boilerplate. The rationale: sensible defaults and dependency injection reduce the cognitive load of setup, letting developers focus on actual business logic.
On runtimes, Java appeared frequently in the context of application frameworks and server environments. Cloud-native approaches dominated responses, reflecting bol.com's migration of existing and new applications to Google Cloud.
Database and Storage Shifts
Data storage technologies showed interesting transitions. Teams moving to cloud-native architectures often left behind older storage approaches that assumed on-premises deployment. The responses suggest ongoing consolidation around cloud database services rather than self-managed database installations.
Cloud storage itself generated multiple mentions — unsurprising given the scale of operations involved. The variety of cloud technologies mentioned reflects the breadth of Google's service offerings and how teams adopt different services based on workload needs.
What This Means for Your Team
If your team is debating whether to invest in testing frameworks, the data suggests you should stop debating and start using them. The developers surveyed work at scale and still prioritize testing tools — the assumption that testing slows you down doesn't survive real-world scrutiny.
For application frameworks, the pattern is clear: teams want sensible defaults, automatic dependency management, and minimal boilerplate. If your current stack requires significant manual configuration for basic operations, you're paying a tax on every new project.
Cloud adoption continues to drive decisions, but the survey shows teams being selective rather than wholesale migrating everything. Workloads that make sense on cloud infrastructure get moved; legacy systems that work stay where they are until migration costs justify the move.
What to watch next
Watch for the specific testing frameworks gaining adoption versus those being abandoned. The community conversation often lags actual team practice — technologies that appear "boring" in conference talks often power serious production systems. If your team is evaluating toolchain changes, the survey suggests starting with honest assessment of what your developers actually use versus what they say they should use.
Key takeaways
- Testing frameworks are well-represented in actual usage even if they get little conference stage time — invest accordingly
- Application frameworks with sensible defaults and dependency injection reduce project setup overhead
- Cloud adoption is selective, not wholesale — workload fit determines migration decisions more than architectural preference
Frequently asked questions
What did the bol.com developer survey cover?
The survey asked 25 developers and 5 technology leaders about technologies they want to learn, technologies they used this year worth learning, and technologies they're moving away from.
What stood out about testing framework responses?
Testing frameworks were prominently represented despite common assumptions that senior developers don't need them — the survey suggests serious teams prioritize testing tools.
What application framework patterns emerged?
Respondents favored frameworks with sensible defaults, automatic dependency management, and minimal boilerplate over verbose manual configuration.
How are teams handling cloud migration?
Cloud adoption is selective — teams move workloads that fit cloud infrastructure while leaving legacy systems in place until migration costs justify the effort.
What database trends appeared in responses?
Teams are consolidating around cloud database services rather than self-managed installations, reflecting broader cloud-native architectural shifts.