coding a startup | devlog 23

Coding a startup | devlog 23

[seanrileyhawkins]

The flow of the video seems pretty chilled and laid back. It's nice just gives a perspective view that a dev doesn't always sit at the desk all day.

[ev]

These "A day in the life of K" style videos work for me. A bit of everything is interesting. Keep them coming.

[ryangatchel]

From my experience if you don't understand something. You could always ask the dev what they did. It's a great way to grow as a developer and what you learn you can pass on to others :)

[Crilic]

Man!!
This is the first of yours that I've watched and you're exactly what I need. I am just starting Python in uni and I'm wanting to program, but everyone seems to convey "You gotta love the dark, be on the screen 8 hours, completely withdrawn, a bit unfit etc." It is scary!

And here's you with the hyperfocus, the fails, the thought processes, the weaknesses, but the intention to get it done despite the struggle, the LIFE outside coding.
Thank you for being a channel that doesn't make me look at the code the whole time but just says "hey this can be what it's like and it's ok to be human".

Thank you bro. Subscribed on tv and personal channel.

[momshaddinury]

Hey, this is dinurymomshad here. :3
Love your videos. I am trying to add the following things to make PRs easily understandable.
1. What I did do?
2. How I did?
3. If there is anything special
4. If possible image/video

Plus hit me up, if you need an explanation. Basically, my main goal here is to keep things in a scalable structure so that it's easier for anyone to contribute. For example, I am currently having a hard time understanding what is done on the calendar and workout page. So if you can make a video on what has been done so far on those two pages, that'd be great.

[TalMusic]

I'm watching your videos for a while.
Never commented but I want to say I love everything I watch.
Keep uploading videos of you sailing, programming or whatever... 🙂
It's so relaxing and inspiring!

[younghan]

a special youtuber for lots of people.
keep posting.
lots of people dont know they worth.
programming or not, always there

[ahmedmaher]

Dude, these unedited videos are gold, keep them coming.

[hasnain]

It was pretty chilled out and really very real kinda stuff tbh. The editing without any bg music is superb.

[intricity]

Kalle - Have you thought about creating a PR template for your repository?

This will make your life easier as a reviewer.

Firstly, it will make it easier for you to parse PR descriptions as they should be in a standard format.

Secondly, you can define a 'Test Plan' section in your PR template. This encourages contributors to clearly list the testing steps they've taken. The test steps should be written clearly enough that you can checkout their branch, and easily follow their steps. If you can't do this, you should reject the PR until the description has these steps! This benefits you and contributors. First of all it gets contributors into the habit of clearly defining their tests, and secondly it allows you to test the work others have done.

Have you also thought about adding build pipeline integration into PRs?

These can be configured so that when a PR is created the build pipeline is triggered, runs the build, runs unit tests and any other automated tests you define. They can be configured with Github so that PRs cannot be merged until the build and all automated tests pass.

Both of these will make your life a lot easier.

From there you can look at adding things such as codecov etc to track what percentage of your code base is covered by unit tests etc.

Spending some time ensuring you have these sort of things automated for your repository will make your life much easier as a maintainer. If you want to start trusting other maintainers in future, it enables them too.

I tried to add some useful links to my comment but youtube seems to delete them.

If you google 'Github PR template' and 'CircleCI PR integration github' the top links should help. CircleCI is free for open source projects I believe.

[lukas]

Hey Kalle, loved the video. Was the first one in a long time, that I really enjoyed watching. Thanks for sharing, keep up the amazing work!

[curtiscrentsil]

I lost your videos, but today I had to find it😂🤝🏾, that's why it's good to subscribe

[tinmancode]

you can always pull the branch of the merge request and run it locally to check that it does not work. What you dont want to do is merge something that is not working because its a bunch of effort to reworkout issues

[eliasavelino]

An Idea apart from designing in Figma is to apply an entire Custom Theme to your MaterialApp, which not only defines a color scheme but also all the UI tweaks and changes for all the UI components. That when you need for example a Button, you just use a vanilla ElevatedButton without any extra styles or themes, and it will already be Themed correctly, same with all other UI widgets. And any changes you make in the Main theme will apply everywhere!

[ml]

Just merging code in without really testing it.. Nice. Way to keep up good practices.

[bekzhanbidakhmetov]

This type of videos are great man! Keep filming :)

[josephmarks]

Enjoying this style of video - well done

[Kfoo-djmd]

I really like the new video formula, kinda long chill videos

[MichaelRinghusGertz]

Sailing part is super nice, make a few videos about your boat. Let us know which boat you have. And then make a trip to Denmark...

[Merrett]

Can you look to build a pipeline or tests to deploy when you merge, I suggest having some branch protection rules and at least run Snyk in your repo to capture OpenSource vulnerabilities and poor/insecure code. Last thing you want is to to be popped or exploited.. happy to contribute - its my day job.