Give this some thought and let us know!
For further actions, you may consider blocking this person and/or reporting abuse
Give this some thought and let us know!
For further actions, you may consider blocking this person and/or reporting abuse
Oldest comments (38)
When something clicked and I went from: Okay I know how to write an algorithm to actually being able to write a program. I did a lot of programming in that period. My work was entirely unmaintainable but my rate of progress sped up greatly, and I just really enjoyed the ride.
Well…not sure it was fun 🤨 but when I was learning Miranda…my mind went through a lot of stages…curiosity, anger, frustration, denial, happiness and finally rest…haven’t code in Miranda since that time 😅
When I first started learning react. It was mainly because of the people I worked with professionally and how much I grew during that time.
Whenever I get to pair with someone on something really challenging, it's super fun! Having someone else to bounce ideas off of and help out is a great experience.
Ohh good one. It is often the human element that makes the difference. For me it can go in either direction: The joy of doing something with the right people or the joy of doing something solo in the right way where the solo part is special.
I've engaged in just a bit of mob programming and it was a lot of fun.
Yes mob programming is so much fun! I think you're right about doing something solo too -- it depends. :)
What is mob programming ?
Here's a strict definition -- usually when I use it I just mean pairing with more than one person agilealliance.org/glossary/mob-pro...
For me it was creating a work queue with simultaneous workers and dependencies between work items. It processed CSV files, put the data in query-able tables. Some tables depended on data from other tables. And the data was not necessarily clean so I had to validate it and store the validation problems. It was interesting to explore the multi-threading aspect, solve queue dependency ordering, and other challenges. At one point I was able to completely saturate our database's CPU and remember feeling proud of that. (Although I think that turned out to be something I fixed later.)
Here's what I can come up with:
As an entrepreneur, there are no shortage of fun programming moments as it's often the result of a lot of inspiration which goes beyond the activity itself.
In the early days of what became DEV, and then grew into Forem, I spent a lot of time thinking and then would code pretty quickly.
DEV was launched the day after I typed
rails new. Rails came to fame from the famous "Building a Blog System in 15 Minutes" demo, so it sort of tracks that the beginnings can come together pretty quickly. It was the clarity on how it might be useful and grow that was more inspirational than the coding task, but putting it together was exciting.Later on, features like comments, reactions, etc. were generally stuff I built in about a day. I actually built reactions while hanging out with @triketora in a little impromptu hack session when we lived in NYC. I definitely remember this more than anyone else, but I definitely felt like I wasn't really engaging in the conversation because I really felt on to something. 😅
At times I've overdone it on the inspiration-driven coding and it's not as useful as it once was for me, but it is one hell of a time.
Current Forem team members and contributors over the years: "Yeah, I can tell a lot of this was built quickly, isn't always so much fun years later".
It was many years ago, during a company Hackathon.
We developed a Chatbot that integrated HipChat with our CI/CD system to tell us the state of builds. It could also tell you what builds were deployed to what environments.
A clear case of "scratch your own itch".
This is back in 2015, very early adopters of the chatbot hype. So tooling and tutorials were very slim. It was a great coding challenge for the group.
Needless to say, we won the hackathon 💪🏻
I remember one time.
Greenfield project first beta version goes to production we are about to release it when somebody realise that we totally forgot about 404 page.
We pinged designers but it was close to midnight and they werent considered as critical members to do release so they were offline and probably drunk :)
All frontend engineers sat infront of the one computer for an hour and put together 404 page with faces of designers with totally crazy animations. I mean that thing had like 30 moving parts and would give you seizure.
Then we got drunk as well
Playing with Sonic Pi while I have little to no musical talent and getting paid teaching kids programming through this or Minecraft using the raspberry pi.
I've always coded things to make my life easier and there are many times I can think of where working through the steps and accessing external services or systems was like a puzzle and solving it and seeing it all run for the first time as I want was fun and a sort of - yeah, I did that - moment.
One of my best was scripting the database restore process that ran early on Sunday mornings after the weekly backups. It would pull down the latest prod copy, import it into our SQL DB Server, then sanitize the data so we never had Customer emails, CC #s, and addresses in there. That kept our QA lab up to date and allowed us to keep testing on the current DB schema.
oh, it was all in Perl....