lucasvegi
Hi guys!
My Ph.D. advisor and I are researching code smells in Elixir systems. This work resulted in the Catalog of Elixir-specific code smells, which has already become quite popular among GitHub users. (https://github.com/lucasvegi/Elixir-Code-Smells).
Now we need your help to identify what are the smells that appear most frequently and have the most negative impact on the maintenance of Elixir systems.
If you are interested in the quality of your code, could you please help us by answering this survey on code smells? (it should take 15-25 min) https://lucasvegi.github.io/Elixir-Code-Smells/
Thank you!
Where Next?
Trending in Discussions
Other Trending Topics
Chat & Discussions>Discussions
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Develop your skills with books, videos, and courses.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 10 of 14 Posts
josevalim
Thank you @lucasvegi! I have pinned to bring more visibility to it.
If anyone has 15-25mins to spare, prepare yourself a cup of coffee/tea and consider filling in the survey.
lucasvegi
Thanks, @josevalim! I really do appreciate it!
Sebb
TIL: my code stinks.
Can you say anything of your plans with this?
lucasvegi
Hello! We have some possibilities with the results of this survey. For example:
Imagine that you have several code smells that are harming the maintenance of your code. Which one should you remove first? Maybe we can answer that question in a few months.
Tools like Credo could be adapted to detect the most frequent or harmful smells automatically. Our research can direct the effort to adapt a static code analyzer like Credo, implementing the detection of the most important smells first.
adamu
I think you may get more responses if it’s possible to preview the questions before submitting an email address and agreeing to the terms.
lucasvegi
Hi Adam, you gave a great suggestion!
A member of the Elixir community (@adolfont) has already made a short video presenting the content of the survey. You can watch it at this link: https://youtu.be/xgvE4GJEFyw (from 2min40 onwards the content of the form starts to be shown)
I know it may seem strange to provide some personal data like name or email, but when we do scientific research involving people, we have to follow some rules of the university ethics committee. This data is used for academic purposes only and will not be made public, as explained in our consent terms.
If you have any other questions, feel free to ask me, ok?
zpeters
I took the survey. I think i just learned a lot about different code smells that i wasn’t really familiar with. Very eye opening to me
lud
It’s tied to a google account. What if someone does not have a google account, or does not want the data to be tied with their account …
I’m taking the survey anyway
lucasvegi
Unfortunately, this is a limitation of the tool we chose to use in our research. While we know this may be an issue for some interested in participating, we believe it will not have a significant impact on our research.
Anyway, I’m open to receive messages from everyone who wants to participate and for some problem they’re not able to
JeyHey
Off topic but still. The term „code smell“ always struck me as crude. Aren‘t there better terms for this ? Or is it just me who has a problem with this word ?