---
title: "Reme Le Hane (@remelehane) | Hashnode"
description: "Flutter Developer. Read the latest articles by Reme Le Hane on Hashnode."
url: "https://hashnode.com/@remelehane"
---

@remelehane

# Reme Le Hane

@remelehane · South Africa · Joined July 2021

Flutter Developer

[Website](https://remelehane.dev/)

## Comments

[Been working remotely for the same time period, and not seeing people is the thing I absolutely love the most. I shall be working this way till the day I die. I don’t get a job to make friends, be social or even be liked. Work is for working, not work is for socializing and drinking and gaming and what not.](https://hashnode.com/posts/4-lessons-learned-working-remotely-for-2-years/62792b3d7f98319956cd2c2f/comment/627c705b4903bec29b585a7d)

Comment · Article · May 12, 2022 · [4 Lessons Learned Working Remotely for +2 Years](https://hashnode.com/posts/4-lessons-learned-working-remotely-for-2-years/62792b3d7f98319956cd2c2f)

[Jordan Holland Agreed, but Dependabot exists purely for security purposes and is an alerting tool first and foremost. It's not often that it automatically creates the PR for the fix and in the end, you still need to approve the merge so it leaves the decision 100% in the hands of the developer, it does not make the choices for you. Personally use the IDE plugin to inform me when package updates are available, I can then open the spec and just click "accept". That way the analyzer has a heart attack if there are breaking changes and I can simply "ctrl+z" and carry on with my life until I feel like dealing with it.](https://hashnode.com/posts/automate-flutter-package-upgrades-with-github-actions/60e3c1574aacd630482416b5/comment/60e6b33dc32fbd1b73720cde#reply-60e6b830c32fbd1b73720f35)

Reply · Article · Jul 8, 2021 · [Automate Flutter package upgrades with GitHub Actions](https://hashnode.com/posts/automate-flutter-package-upgrades-with-github-actions/60e3c1574aacd630482416b5)

[Just curious, what is your reasoning for wanting to automate this, packages are one of the few things that should be managed manually. The risk for breaking changes is pretty high, even in a well-tested application. The problem is many developers do not understand the purpose or meaning of semantic versioning and I have personally seen breaking changes come out with patch and even build releases, developers rewriting entire API's and publishing as a patch release, and this was not even on pre-V1 releases. One package, I recall 2.3.3 was working perfect and 2.3.3+1 had a new API. lol. While in theory this is a good idea, not sure it's something one ever wants to put into practice back in the real world.](https://hashnode.com/posts/automate-flutter-package-upgrades-with-github-actions/60e3c1574aacd630482416b5/comment/60e6b33dc32fbd1b73720cde)

Comment · Article · Jul 8, 2021 · [Automate Flutter package upgrades with GitHub Actions](https://hashnode.com/posts/automate-flutter-package-upgrades-with-github-actions/60e3c1574aacd630482416b5)

[God point you made there, I should add that bit in. Reminds of of the wasm file I forgot about for canvas kit users, that’s an additional 3mb onto the payload.](https://hashnode.com/posts/flutter-web-should-i-use-it-part-2-performance-d801d122fc3e/60dd38d495305075b9338a32/comment/60e056fc4f8e376422a77504#reply-60e059a34f8e376422a77568)

Reply · Article · Jul 3, 2021 · [Flutter Web: Should I use it? (Part 2— Performance)](https://hashnode.com/posts/flutter-web-should-i-use-it-part-2-performance-d801d122fc3e/60dd38d495305075b9338a32)