
Daniel Jacobsen
@CodeIntegu
Hi, I'm Daniel 👋🇩🇰 💻 #Java ☕ and #Android developer 📲 ▶️ Sharing my journey & guidelines to become a better developer
你可能會喜歡
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: integu.net/electron-vs-nw… 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.
When is it ok to comment your code? donnfelker.com/code-comments/
donnfelker.com
Code Comments
When it’s it appropriate to comment code? I follow a simple set of rules: The “why” explains WHY the code exists and perhaps some important and relevant details that might not be evident to future…
Good point 👇😉
Copying from the official documentation and changing a few words here and there seems to be a very popular way of writing tech blogs 🤔
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.
Short and simple blog post, illustrating the difference between the various ways and method of developing mobile apps.
Flutter, React Native, Ionic and Native platform: A visual guide ift.tt/2H4VUDh ift.tt/2yWVwlR @flutterdev #flutterdev
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.

Pretty sweet workflow. Great ambition to set for any bug fixing issue.
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: buff.ly/2G5e0Ex 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 maxpou.fr/busting-nomad-…
What to do when the code is quacked up 🤣
Perhaps you are looking for a summer read? Developer Books ▶️ buff.ly/2JyWucV 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 buff.ly/2NxObTW #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?

Wise words 👌
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: buff.ly/2WGXp0e

Daily stand up: Short and to the point. 👍✔️
An effective stand up should be # of participants * 1 minute each (hard cap at 60 seconds) and should never include more than 7 people. So, never more than 7 minutes optimally. If something/one needs additional details, keep interested parties afterwards and release the rest.
United States 趨勢
- 1. Pico Prism 4,057 posts
- 2. Stanford 11.7K posts
- 3. Good Sunday 40.6K posts
- 4. SPENCER SMITH 1,117 posts
- 5. Norvell 4,413 posts
- 6. Florida State 10.6K posts
- 7. Brendon 6,459 posts
- 8. Sabrina 70.8K posts
- 9. #AEWWrestleDream 71.9K posts
- 10. Manchester United 41.8K posts
- 11. lorde 7,271 posts
- 12. Utah 33.4K posts
- 13. José Gregorio Hernández 42.9K posts
- 14. Darby 11.9K posts
- 15. Shatta Wale 41.3K posts
- 16. Talus Labs 13.2K posts
- 17. Vaticano 39.8K posts
- 18. Lott 1,025 posts
- 19. Hugh 9,736 posts
- 20. Nobody's Son 5,656 posts
Something went wrong.
Something went wrong.