I've been posting these since time immemorial 9 months by now. Since almost the first post my plan was to hand the responsibility of posting them over to someone; as of recent it seems to me that soon I'll lack the time to properly participate in them as the organiser that keeps the discussion alive and fruitful. In fact, the last few posts I've either posted one comment or none at all.

So maybe the 25th or the 26th topic should be posted by the New Guy™? Has the time come? My answer is yes, TBH. In the comments, you can criticise my decision, call me lazy, or name yourself as a candidate freely. I guess we'll use votes on candidate comments to determine the next guy. If there is a tie, I'll name one of them as the next guy (tell me in the comments if you disagree with this). Voting will be over roughly when this post becomes three days old. I don't think too much precision is required, or else we can try something else.

IDK if this is a nice way to do it, but I don't want to do this Guido van Rossum style—say "bye, figure this out for yourselves, you lot" and leave. Hope I'm not over- or underdoing it. I'll ask a few prolific posters to name themselves as candidates through PMs.

Edit: I'll close voting around 3 PM UTC+3 24th of July, which means I'll edit to record votes I see by that time, including a timestamp. I'll then speak to the user with the highest amount of votes, informing them of the (rather simple) process of posting and maintaining these threads. Most probably, from #25 onwards, the new guy will take over.

Thanks a lot for taking this seriously and helping this nice feature of ~books move on with a new maintainer!

Edit 2: I'm closing votes, it's 24th of July 2019, 18:20 UTC+3. @acdw has 10 votes, @iiv has 6. I'll contact @acdw, and the next WAYRC topic will include an announcement. Thanks a lot for your participation and interest in the future of this fun little thing we do!

Today I found a girl

Who was pretty nice

To me.

She made me stop and talk

And rest

and breathe.

She said your stomach growls,

Your legs

Are weak.

How’d you like to come

And sit

With me?

.

And my how time it flew

And passed

Us by.

Lunch turned into tea

Turned in-

to night.

The way her body curved

It shaped

My mind.

And then her laugh,

Her smile,

Her eyes.

.

Would you mind if I stayed

For an hour or two

Or three?

We could sit and talk

And laugh

And crawl between the sheets.

And maybe I can stay the night

Or two

Or three?

And you’ll hold onto me.

And we can spend forever

Cus talk

Is cheap.

And maybe nights will

Slowly carve a curve and crash on

Into weeks.

Maybe we’ll be cuddled

On the couch or sipping

Sex on the beach

Maybe I could stay

For life, just

You, and me.

I think having a hobby, something outside of your work that you enjoy doing and/or are simply just good at, is kinda important, and fulfilling. And so, I wanted to make a topic in general about what hobbies you might have and why that particular hobby appeals to you (along with some tips as to how a newcomer might be able to introduce themselves to the hobby).

For myself, I have recently gotten into the Rubix Cube and have had a lot of enjoyment learning some different methods and improving the time it takes me to solve it.

Started out with a non-descript cube from a supermarket and have recently purchased a GTS3M which I am enjoying a lot so far (plenty of online stores in a variety of countires that will deiver quickly and cheaply). I was able to find a plethora of tutorials on youtube (jperm and brodythecuber in particular) that I found very helpful. For any other cubers: favourite perms, methods, do you compete, tips?

Something, something first post, may not be perfect, but I want to be more engaged.

Hello! After spending many development hours in my past years running on Virtualbox/Vagrant-style setups, I've decided to take the plunge into learning Docker, and after getting a few containers working, I'm now looking to figure out how to deploy this to production. I'm not a DevOps or infrastructure guy, my bread and butter is software, and although I've become significantly better at deploying & provisioning Linux VPS's, I'm still not entirely confident in my ability to deploy & manage such systems at scale and in production. But, I am now close to running my own business, so these requirements are suddenly going from "nice to have" to "critical".

As I mentioned, in the past when I've previously developed applications that have been pushed onto the web, I've tended to develop on my local machine, often with no specific configuration environment. If I did use an environment, it'd often be a Vagrant VM instance. From here, I'd push to GitHub, then from my VPS, pull down the changes, run any deployment scripts (recompile, restart nginx, etc), and I'm done.

I guess what I'm after with Docker is something that's more consistent between dev, testing, & prod, and is also more hands off in the deployment process. Yet, what I'm currently developing still does have differing configuration needs between dev and prod. For example, I'd like to use a hosted DB solution such as DigitalOcean Managed Databases in production, yet I'm totally fine using a Docker container for MySQL for local development. Is something like this possible? Does anyone have any recommendations around how to accomplish this, any do's and dont's, or any catches that are worth mentioning?

How about automating deployment from GitHub to production? I've never touched any CI/CD tools in my life, yet I know it's a hugely important part of the process when dealing with software in production, especially software that has clients dependent on it to function. Does anything specifically work well with Docker? Or GitHub? Ideally I want to be avoiding manual processes where I have to ssh in, and pull down the latest changes, half-remembering the commands I need to write to recompile and run the application again.

Let's do a little show and tell for our new toys :)

(I was thinking about this as a non-recurring equivalent to the listening threads and such but I probably worded it a bit too...fluffily for ~tech so I moved it to ~talk)