Had the opportunity to research pros and cons between "web-integratable-desktop-applications" solutions like Electron, NW.js, and CEF.
My findings have been summed up here: https://t.co/KlkB8RvxZI
Hope it can help out others. 👍
#Electron#Nodewebkit#Chromium
Agreed.
The WHY is so much more important than the HOW.
If it is necessary to write how the code works it is probably worth making the code more clean. Extract a method here, make a local variable there. Explain what is happening.
Arguably learning new skills on a consistent basis help you develop an versatile T-shape profile.
I still believe that you should have one core skill, which can be used to support all other.
Learn a new programming language at least every year.
You'll broaden your skills and opportunities more than you can imagine.
Specialization is for insects.
Joke aside.
Knowledge hoarders only shame people asking for help when they are afaid of being caught up to.
Look for the people who are willing to share.
These are the once who ever stop learning, and are therefore not afaird to spread knowledge.
Stack Overflow's great when people choose to demonstrate their intelligence by insulting your approach rather than answering the question or providing substantive guidance.
So...#Flutter? Is it the new holy grail of mobile app development? Perhaps?
Yesterday I participated in a TechTalk at @ZliideLtd, which utilizes Flutter to create their cross-platform app.
Interesting event and technology. I would highly recommend taking part.
@javinpaul 1. Start a hobby project, which you are passionate about.
2. Go out of you way to implement all the concepts you learn.
3. Forever have documentation of you professional progress.
Forgot something? Check-out your project. 👍
My preferred workflow when fixing a bug:
1. Can I write an isolated, automated test for this bug? If not, refactor so I can.
2. Write failing test
3. Fix the failing test
Now I have:
- Proof the bug is fixed 🐞
- Documented expected behavior 📃
- Regression protection 🥽
#tdd
Using enums as an alternative to booleans, can sometimes be beneficial.
Blog: https://t.co/iktWNMmbmq
1. Increasing the codes readability.
2. Instantly conveying the point of the method argument.
Short and valuable blog by @codinghorror aka. Jeff Atwood
Great blog post, @_maxpou 👍
Remote work is not the equivalent of sitting at the beach and drinking mojitos all day. (aka. holidays)
Opportunities like this requires lots of work, weird time schedules, and risk taking.
Hope to see more content like this 😉
📝 Digital Nomad: the Golden Ticket?
🗣 Working from the beach, constant traveling, "you must be rich"...
🙅♂️ I wrote a blog post to debunk some myths about this lifestyle because Instagram is not the real life!
#digitalnomad#remotework#bullshit
https://t.co/b6NSnMVvtk
Perhaps you are looking for a summer read?
Developer Books ▶️ https://t.co/lPuB4WIsBr
Just finished up making a " #Developer Book" review page.
I categorized it as "Developer" and "Technology and Business", since I also have a few different recommendations.
#Programming
"Tests are an oracle. Oh great oracle, what will happen if I deploy now? Disaster, my child."
Short and to the point article.
Programmer Test Principles by Kent Beck https://t.co/q51tpyw6GP
#Developer
During my latest #pairprogramming session, I caught myself going down the rabbit hole of writing code on my own and just discussion my thoughts out loud.
At the point of realization, it was unfortunately too late. The constructive dialog had already died.
How do I avoid this?
Got a #Developer book recommendation?
Currently writing a short list of my personal book recommendations for my blog.
Hope that people are going to find it useful and gain some value from it.
Perhaps you know a book which I should include in the future?
Funny comment in the code (#CleanCode anti-pattern)
// FIXME: throw the exception, I am not making the change
// now because I am concerned I may screw some tests that rely on this
// behavior
I remember what @VictorRentea said once, "when you fear something, do it more often" :)
Interesting survey and report by @CollaboratorSB
Knowledge sharing and manual walkthrough of code is apparently still seen as the best way improving quality of code.
Personally I agree, how about you?
My opinion: https://t.co/vjnsQYf8eb