Just a last thing. Try to think at this from another perspective :

Imagine you have a pet project. Imagine that project is a social network for fans of Marvel charachters. You decide to call it "marvel-heroes" and you put all tour time and effort to build the best app you can. You add tagging features and chose without thinking the name of the app itself to post your first welcoming messages for the community.

Then release day happens. Fans of Marvel are starting to subscribe. A lot of them start to reuse the tag you created because it says exactly what they're came here to talk about : "marvel-heroes".

But that was not the usage you decided for this tag. So you're frustrated. And because you're frustrated you will not see that you just made a simple and easily fixable UX mistake. And so instead of fixing it, you'll start throwing (explicit or implicit) rules at your users and yell on them if they don't follow it.

All of this is ridiculous. Since many years now.

All that being said, changing that tag name should be considered only because saying "devrantrant" is much more fun anyway.

Honestly ? I still come here once in a while only to read "stories" for a few minutes. There still are great things written there. The home feed is really different. As it's the main view of the app we could expect to see quality content on it. And that's not the case.

Some will say it's because of the memes. Or because of the newbies. Or because "people are stupid".

I think all of these statements are wrong. From my perspective the main problem of the home feed is really that it is BORING. I'm not lying here : EVERYTIME I open the app I feel like 80% of the comments I'm reading are about that "devrant" tag. And maybe once a week there's a thread like this one, throwing questions into the wind and baiting the most frustrated nerds among us to come and vomit all of their hate against the "noobs" and the "stupids".

Honestly I'm here since enough time to see there's an obvious pattern here. The intelligent solution is to break it. Kill the source of all that drama. That's just a tag.

Okay man, boring as fuck, as always. So much possibilities thrown away by that circlejerk way of thinking but okay.

I'm a dev and still I like communities that are capable to be friendly and to evolve. This place can't do any of those things because it's trapped in a loop about the same boring and useless points of details. In France we have words for that, we say "enculer les mouches".

This community sacrifies its ability to evolve and to be friendly and welcoming, just to fuck flies.

Keep going. I'm bored enough for the next six months.

So many years, that same boring problem again, and still nobody to come with a real solution. Change that bloody "devrant" tag for something more specific. Update existing data if needed for consistency. But for god sake everybody, if you consider yourselves as people paid to find solutions, please, please do better than this endless loop of useless drama ans accusations that should be so easily avoided.

The quality of this community could have been so much better since years now, just by changing this tag once and for all. No more need to warn the newbies. No more drama. No more same boring thread every week.

Or you may just keep going with the endless fight. Sad choice, but hopefully life continues outside of here.

If I may,

I subscribed a long time ago, never really been an active member. But once in a while I open the app an scroll to see what's new. And very often there's nothing new at all : it's the same boring self-centered threads about how memes are the invader from outside, the same "the devrant tag is not for ranting" and other infinite loops. This community is boring and spoiler alert its not because of the memes or the shitpost or the newbies : it's because of gatekeeping jerks who seems to have nothing better to do with their lives than looking for some social validation on a web app.

That beeing said, that's only my point if view and i'm not opposed to anyone here. Actually I'm going back yo silent mode. Bye devrant.

@Fast-Nop Thanks ! That what my first thought but I still had a doubt... You reassure me, the opposite would be so painfull ^^

I made the version with emojis actually. Yeah I could have added a lot of smileys/emojis variations, I thought about it but I felt too lazy at the moment to spend more time on this ^^

@mkopter This thing is so usefull, thanks! Bookmarked.

Missing a third reply :

"Okay then: sudo git push --force"

@windlessuser Found that report you mentioned, sadly I think I was expecting more detailed information. Reading this I feel like the essential part is merging small commits in master very often. So I think that goal still could be achieved with git flow, just by cutting tasks in smaller features. That way you still have feature branches (and the pro/cons coming with it: you'll need to remember about rebasing it regularly but it will be harder to mess with history by accident), but these features branches are the smallest possible so you don't keep working on the same for too long.

Finally I think like this is much more a matter of how you can break your features list in smaller features, than using features branches or not.

@windlessuser But how does that applies to very large teams ? If you have 15+ devs on a same project, then they all stop their current work to focus on that single issue introduced by only one of them ? Or only 2-3 of them are working on solving problems while the others are waiting it's solved ?

@windlessuser Thanks, I'll look into this. But on my first opinion the "it needs discipline" argument is not strong enough: after all you still need discipline to produce quality code, to not push the wrong code on the wrong depot, and so on. It's just one habit amongst many others. And without more information about that, doing everything on master seems like risky... Unless you add... well, some discipline here too.
But you still made me curious so I will read about it ^^

@windlessuser You could also address that issue by taking the habit of rebasing your feature branch every day. Git-flow helps a lot.

I learnt git basics 4 years ago, using command line. But since I feel comfortable with it I'm lazy, so I just use SourceTree. It has many ui bugs but it does a great job as an everyday git client. I could go back to cli but it would feel uselessly painful.

But the real thing I love is git-flow. That simple workflow totally change the game: it's so clean and efficient, it simplifies team work a lot, it helps using semver, and once you get it it's actually a very obvious way to work.

@VinzuSama

I experienced a combo of #3 and #5 with some friends. It's enough to fail.

But for the history, I'd also add "get up at 2:00 PM every day when you have clients"...

These days I would say GraphQL > NoSQL. At least for the hype around it.
If you already find NoSQL addictive, go take a look on this: https://www.prismagraphql.com/

Don't wait to learn how to say no to a client when you have to. Because you will be facing different kind of situations where this will be your best move, but it's not always easy to do. Learning how and when to do this will avoid you some mistakes I made when I started freelancing at the time (trust me you don't want to know that feeling when you have to anounce to a client that you fucked up his deadline).

Start by little projects that you can achieve quickly and with quality. That will help you to gain confidence and good practices, and soon you'll realize you've reach a point where you can handle more ambitious projects.

Also, try to adopt work hours even at home. That too is not always easy (I love so much coding during night) but you'll be more productive.

@agaskins This. I quit my last job as an employee after only 5 days because of this behavior from my boss. Since day 1 I was experiencing a lot of trouble with their internal tools and process. I asked for help a few times, but nobody had time for giving me anything else than quick advices. Hours where passing while I was litterally waiting alone at my desk facing shitloads of errors after trying to do simple things like cloning a repo which they wanted me to work on. There really were bugs, permissions issues, and a really shitty devops, things that I couldn't manage to fix by myself after only a few hours on the job! So I adressed the problem with boss, and he said that I was not good enough, that they had warn me about the fact that the team had a pretty good level so it would not be easy for me, and shits like that. Please dude, you make shitty drupal websites! Did 5 days, nothing changed. Actually boss attitude with me was worse, so I left, and I'm much happier as a freelance now.

You're right, I should have used "its" instead of "his". Let's say that's because I'm french!

And of course now I want to say how deeply I'm sorry to every rendering engine, or their relatives, that were hurted by my statement in any way. Peace to all softwares on earth and beyond.

And then kids, all the nonsense started right there in 2018, when the first CSS rendering engine claimed his right to be identified as a C++ compiler...

@Froot For a static blog, I also think that totally makes sense.

@Masta Bonus part: with ffmpeg you can use your icecast stream as audio input, merge it with images/videos of your choice and then push your "radio-in-video" stream directly live on social video platforms like Facebook live or Twitch.

(I made it work on Facebook, it streamed about 5 hours before they automatically censor the stream because of music rights. If anyone knows how to contact them to discuss this... I'm really interested!)

There's also a few webradio servers that are written in node, available on github, if someone wants to try new things. I didn't test any of those.

Oh, and if Liquidsoap is really too painfull for you (which I can perfectly understand), you'll may want to try Libretime (fork from Airtime). Basically it's like a frontend for Liquisoap, with a web admin platform.

I haven't tested it so far, since I wanted to do things on the lowest level possible in order to really learn new stuff (and not just using a UI). I managed to achieve what I wanted to do that way, and I'm happy with it.

But for more complex configurations than mine maybe you'll want to try Libretime.

@monkehparade

And sorry but, as much as I would love to share the url, for the moment I prefer not to, since I don't pay for a diffusion licence. That's actually really affordable here in France (80€/year: https://clients.sacem.fr/autorisati...) so I will definitely do this in the future, just to make sure that my little webradio is legal and that I can share it without worrying. Actually the radio is intended to be on a community website (I will not say "social network", fuck) which I work on as a side project. So I wait until that project is ready to open to engage myself with the radio etc. In the meantime, sorry but it's only for me :)

@Masta

(...)

But the good new is, hey, all of this runs on linux, as developers we (should) know linux, so we can always find a way to achieve what we need. I mean, I started about a year ago with a much more complicated LS script than my actual. Over time, I delegated a lot to cron files an shell/php scripts. Because I have more control on things that way, and because it's often simpler anyway.

So my advice at this point is the following: give it a try, work on it for an evening of your free time, and you'll see it's sometimes frustrating but not so complex.

I'll may consider to write such a tutorial myself one day. In the meantime, if you have some questions please ask and I'll try to help you as best as I can :)

@monkehparade Unfortunatly I can't remember any tutorial in particular that really helped me. I essentially struggled with Icecast and Liquidsoap documentations, and googled a lot.

The Icecast part is easy. You can have it running minutes. As a streaming server it will stream your audio source to the web, but to actually build one (with playlists, jingles, direct diffusions and such other cool things), you'll need another application (a "source client" in Icecast jargon). That's where you'll need Liquidsoap. Basically it lets you write a script file with instructions in order to create your playlists, manage your log files, handle input streams, etc. And it's actually the hardest part, as LS documentation is such a pain in the ass.

(...)

@BindView I use soulseek to find and download what I want (not very legal but I don't really care about that), and for the radio only mp3 files in 256-320 kbps (actually I stream in 256 for the moment but I'll may want to have a better quality later).

@Froot I'm sure if we look for it we can find things that you do more "devly" than me ;)