And here lies the problem: AI may degrade our ability to think things through thoroughly so making clear requirements might become harder in the future. In this fast-paced world, donโt forget to use the old-fashioned "pen and paper" sometimes. Otherwise, as they say, you will be replaced (by AI).
But on the other hand, someone still needs to define the requirements - as clearly and strictly as possible. Without them, you won't get exactly what you expect the tool to build for you.
Nowadays, we have tools that greatly accelerate software development. Literally, they can increase productivity by 100 times. What used to take me months to complete, I can now implement within an hour. That's fascinating!
Ever needed to recover the original commits inside a squashed commit weeks later? Git doesnโt support this out of the box. We built an extension that does - github.com/widefix/squa...
Enjoy and share your feedback!
Received this email today.
What are your thoughts? Do you see or experience the same issue?
These roles are overwhelmed with responsibilities and can't keep pace with new innovations, lacking sufficient time to thoroughly test everything and provide feedback. It's fascinating to consider how this imbalance will be resolved soon. It presents a significant challenge for the current market
At the dawn of the AI age, I've noticed an intriguing pattern: a shortage of tech tickets.
IT solutions are designed for human use, so it's essential for people to validate their quality. While developers have tools to accelerate tech creation, QA and PM roles are becoming a bottleneck.
Store Rails migrations in DB to keep track of phantom migrations and make schema current
๐ Productivity is what I love most about building apps with ๐๐ฎ๐๐ฒ ๐๐ง ๐๐๐ข๐ฅ๐ฌ. But that's not all. What excites me even more is pushing it further and making it an even more powerful tool. Enjoy the new release of ๐๐ฐ๐๐๐ฎ๐๐ฏ๐ฆ๐ฐ๐ต๐ฒ๐บ๐ฎ widefix.com/blog/actuald...
My 10-year-old son couldnโt come up with this idea - mostly because he lacks experience. But what is experience? Experience is simply a collection of failed attempts.
Fail, learn, and eventually, success is guaranteed.
Why am I talking about this? First, in my opinion, itโs a very contemporary example. It clearly demonstrates that AI cannot solve all our daily problems, especially very tricky ones. It can be a good starting point for brainstorming, though. Second, human experience cannot be replaced.
How could I, being an IT guy, not try those tools? Nothing worked until my own idea came to me spontaneously, after trying different approaches and searching for tools around my flat.
In just 15 minutes, the needle was out. I didnโt really believe in the plan, but it worked.
That wasnโt the only idea I tried, though. Before that, I had several unsuccessful attempts: using tweezers and a screw didnโt work; asking AI and Google didnโt help either.
I searched the internet and asked AI, but nothing was helpful. It looked like a dead end. Then another idea came to mind: coat a wire that fits inside the needle with super glue, insert it into the stuck needle, wait for it to bond, and then pull it out. Surprisingly, the plan worked perfectly.
Today I solved an issue I normally wouldnโt encounter. My daily job is to resolve problems related to IT projects, but this time I had a unique request - from my son. While pumping a ball, the needle broke into two parts and got stuck inside the ballโs valve. The needle was already too deep inside.
Correct, so only around option is available.
Thanks! It's looking good and I see it would work indeed. Unfortunately, it has no option which would allow me to do stubs in "before" block as usually done in rspec.
Stub env var in RSpec.
Ran into the same issue again today: stubbing environment variables in tests. I needed a clean and convenient solution. Have not found any worthy gem. Fortunately, I've solved this problem before. And the solution is very simple. #ruby #spec
RubyToolbox is hosted on Heroku
TIL: RubyToolbox is hosted on Heroku. #ruby #heroku
Moral: to be productive, utilize all the tools you have, and don't waste your hours waiting for feedback from long-running tasks. Don't waste precious time. In the end, only the result is important, not the time spent!
And I achieve that with this little hack. Result is 100%, client is happy, my kid is picked up on time - he is happy (I hope so), my laptop can rest, it is happy too, I guess.
I wrote a simple script, scheduled the task, closed my laptop, and picked up my kid from training on time. That's why I'm in the cafรฉ now - waiting for him. But I don't want my limited time wasted. I want this time spent with 100% result.
So what do I do? I have an answer today - just run a scheduled task via Heroku scheduler (devcenter.heroku.com/articles/sch...). Schedule it once a day and remove the schedule in a few hours when the script is stopped. That's it!
I still had no idea how to run long-running processes without the risk of the connection dropping. I don't want to have these long-running processes on my laptop - I might want to close it, pack it into my backpack, and go home from this cafรฉ where I am writing this message.
While I learned from my mistakes in terms of keeping the processes and making the script idempotent (so that when I repeat it, the process continues from where it stops and does not perform the same actions twice).
Nevertheless, I followed this way and it worked. Thanks god the users didn't need to receive the emails thrice!
That's a story from several years ago.
Today, I faced the same task.
Well, naturally, we can split the job into several parts and run them one by one or in parallel. But still, having the scripts run via the Heroku console from a terminal is not an option, as the connection can drop on my side too.
But that's not so bad to bombard users with the same (very useful, though!) email. The main challenge was still there - how do I run this script properly on Heroku if the connection drops in 1 hour, but I have an operation that takes more time?
It turned out there were over 1 million users to whom I needed to send emails. So, in 1 hour, the connection dropped, and I had no idea where it stopped. Some users received emails, and some did not! Repeating the script again would send duplicate emails. What a fault!
Work in a coffee shop
My son training
Heroku run long-running command properly
What's the connection between Heroku, my son, a coffee shop, and productivity?
Once, I asked to send mass emails from Heroku via a script. How dare I connect to the console and run it there! First of all, I made a mistake in predicting the operation.
