Subduction Retrieval


I talked to a guy a while ago...he trained to be a drupal dev for years...and is still learning...meanshile AI for me personally made the devs obsolete....i havent asked any devs for support for over 1 year....so people wake up.....use AI and stop paying devs
i think we reached the stage where developers are not needed if you have like medium knowledge of drupal...you know how it works, how to update etc....i used google gemini the whole time to upgrade....and it gave me all the right answers...before i wisited slack channel all the time...some poeple there are toxic af.... and you had to beg somebody to help you...and even then they could not help. Google gemini is way better then developers from my optinion and I havent visited slack for support now for over a year....gemini knows everything
If you have experience Full Stack development with 1 or more than years, You can real coding with MVP build, SaaS Development, Zoom meeting etc. You believe you are real developer and wanna change make real product, work.
Quick Specs:
Pay: $20β50/hr (depends on your stack/skills)
Vibe: Fully Remote & Part-time friendly
Goal: Work that actually impacts the product
Location : EU, America, US
Interested? Leave a message. :)
| I've been building Drupal sites for a while and the persistent "There's a new version of Drupal" or "There's a new version of the theme" errors in all the admin pages has always driven me nuts. I get that security updates are important, but I really don't think it's necessary to constantly be nagging admins about it. Especially when there are legitimate reasons why you haven't applied updates. After a while you start to cognitively filter it out. It contributes to "alert fatigue" and I think is an overall detriment to the Drupal site building experience. Is there some back story about why you can't permanently dismiss the alerts or at least snooze them? Does anyone have a good module recommendation to do so if someone's tried? [link] [comments] |
| submitted by /u/mherchel [link] [comments] |
| Last week I posted about a new module I'd built and published (in beta) that helps the contributors / editors of long-running sites visualise how their content has changed over time. It's called Content Metrics. I'm building it for my team in the Maths Department at the University of Cambridge, but of course I'm designing it to be useful to pretty much any Drupal site. Since my last post, I've done loads of little improvements. The biggest is an overhaul of the filters. I've moved the filters that apply to all charts to the top (as you can see in the screenshot), and made some of them into autocomplete inputs. And I've added 2 new charts:
My team liked it enough that they asked me to deploy it to one of our larger sites so they can use the info for their reporting to our stakeholders. I'm keeping it in "Beta" state for now since it should be evaluated by the community to make sure it's stable and secure. Give it a try and let me know if there are ways I could improve it for your use case π [link] [comments] |
| If you are running a simple site and want some insights into its traffic with zero configuration, or you feel overwhelmed by the complexity of Google Analytics, or you simply respect usersβ privacy and definitely do not want to show visitors yet another cookie consent popup, there is now a module for that. [link] [comments] |