- Books, generally speaking, have changed my life for the better. I curate my reading list and only mindfully read what is beneficial to me.
The more I practiced mindful reading, the better I got at many things (from work, finances, to friendship and marriage).
I can attribute this to what seems pretty obvious - apply what you learn or think deeply about it to understand its meaning to you.
- For the last couple of years, I've only had these directories: dev, test and prod.
Whatever I am working on or learning goes in dev, whatever is ready for testing or experimentation goes in test. Everything else goes in prod.
But I have been thinking of expanding on this.
Thanks for sharing the article. I might gain some inspiration.
- Gave it the prompt "novel idea" and of course I meant this[0] just to see what would happen. My expectation was that it would seek clarification.
Instead, it proceeded to give me plot twists, genre-bending narratives and premises all based in my country and city.
- I maintain physical and digital notes on my coding. Since I review them frequently, I find them helpful. The notes help me track progress or try out new ideas. Sometimes the very acting of writing reinforces my understanding of new and even old concepts. I would recommend most developers keep a journal of some sort and review it regularly.
- It sounds like you would find benefit from Linux Mint[0]. I recommend using it for a few days and seeing if it fits your workflow.
8+ years of software engineering and project management experience.Location: Lusaka, ZM. Remote: Yes Willing to relocate: No Technologies: AWS | Django | React | PostgreSQL | Git | Figma LinkedIn: [0] Email: danny [at] arcariusmexen [dot] comCore ethic - timely and collaborative delivery.
Open to:
- Contract
- Part-time
- Full-time work
Currently working on an open-source project [1] and looking for work.
Project details:
- Invoice and Receipting System
- Django, React and PostgreSQL
- Q2, 2023
- Hm, I would not call this 'The Lone Developer Problem' but maybe 'Future Comprehension Anomaly' wherein an author today understand their rationale for a design implementation but months down the line, it is as alien to them as it might be to a completely new set of eyes.
One solution is to leave meaningful comments that explain a thought process or design decision where it counts. This nudges future readers of the code in a direction towards total comprehension of the source.
- Before I knew that there was an actual term for it[0], I would get a blank piece of paper, pretend I was an esteemed professor teaching whatever it was I was trying to accomplish. I would "ask my students" questions and "hear their answers". Then I would "guide them to the correct path".
- Not laid off but I quit my job 7 months ago to start my own company.
Just the admin of setting up and running the day-to-day has taught me a lot.
But the biggest lesson I learned is that I have the capacity to research and implement technologies new to me in relatively short amounts of time to make meaningful impact.
In addition, my confidence has improved and I am more likely to accept challenging work within my domain than ever before.
What I am doing running a small business is not cool in the context of the OP and the discussion, but it's cool to me in the sense that I did something I once feared and stuck with it.
Thanks for sharing, everyone. Really cool projects. Take care.
- The key is knowing how much preparation is required to start. Personally, I lean more towards “just enough to start”. Then I flesh it out as I go, if I hit a brick wall, then I pause “to prepare” for the next go.
What this does is ensure that I always have enough to get a task done as opposed to overindulging in “preparation” at the cost of real progress.
Good luck, everyone. Wishing you success 2023.
Cybersecurity - SOC, Incident Response, GRC
11 years experience.
[bssgn1272][at][gmail][dot][com]