Giter Club home page Giter Club logo

codeandbeyond's People

Contributors

soulim avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar  avatar

codeandbeyond's Issues

Product discovery

Outline

Intro

Hello and welcome to a new episode of Code && Beyond. A podcast where we talk about software development and anything beyond that.

My name is Pablo and as usual I'm here with my good friend Alex.

Today we have our first returning guest, Ana HernΓ‘ndez last time we talked about SEO with her and this time she has come back to discuss a very different topic: Product discovery.

But first, Ana please introduce yourself again.

Highlights of the week

  • Alex: TODO
  • Pablo: TODO

Q/A

  • Last time you came here we came here we spoke about SEO, how did you get into product management?
  • Where do product ideas come form?
  • How do you decide which ones to start working on?
  • How do you get the team on board?
  • I guess you don't just start to development them straight away, what are the next steps after you decide which idea to pursue?
  • When do you incorporate tech/devs feedback?
  • How/when do you decide if the idea was successful? What if it wasn't?
  • Summary

Outro

Okay! That's it for today. Thank you for listening! πŸ™‚

In case of any questions, simply send us an email at "codeandbeyond at protonmail.com". You will also find the address in the show notes.

If you are listening to our show on Spotify. Don't forget to leave us a rating!

Keep being amazing! Bye! πŸ‘‹πŸ™‚

Meta

Title

TODO

Show notes

TODO
---

Have any feedback? Send us an email at <[email protected]>.

Check other episodes of the podcast at <https://codeandbeyond.rocks/> and don't forget to give a rating on Spotify ;)

*Music by [penguinmusic](https://pixabay.com/users/penguinmusic-24940186) from [Pixabay](https://pixabay.com/music).*

What does that mean to be a hacker?

Outline

Intro

Hello and welcome to the a new episode of Code && Beyond. A podcast where we talk about software development and anything beyond that.

Recently I had a chance to organize a Hack && Tell event. If you don't know what Hack && Tell is, I'll quickly explain it. It's basically a chance for people to present their pet projects. Every presenter has 5 minutes to present and then 5 more minutes to answer questions from the audience. The presentation isn't an elevator pitch, but more like a live demo of your project and it's always to show some cool parts of the source code.

I really like Hack && Tell format because it has simple rules and allows people to show what they are passionate about. It's incredibly inspiring.

Today we are going to talk about hackers. Not those, who break into computer systems to steal secrets, but those who eager to learn, explore, and try things. Those people who delight in having an intimate understanding of the internal workings of a system. True hackers, I would say.

My name is Alex and as usual I'm joined by my good friend Pablo. Hi Pablo! πŸ˜„

Highlights of the week

  • Alex: Microsoft MakeCode
  • Pablo: TODO

Special section

If you are listening to Code && Beyond on Spotify and like what we are doing. Let us know by leaving a rating on the show page πŸ˜„

Q/A

  • Do you know there is an RFC that defines the term "hacker"?
    It's "Internet Users' Glossary" or RFC 1983.
  • Could you call yourself a hacker in terms of RFC 1983?
  • When you work on project do you like deeper into used systems/tools/technologies just to better understand them? (even it that doesn't bring any value to the final results)
  • Isn't every professional a hacker in their area?
  • Hack project stories
  • Summary

Outro

Okay! That's it for today. Thank you for listening! πŸ™‚

In case of any questions, simply send us an email at "codeandbeyond at protonmail.com". You will also find the address in the show notes.

If you are listening to our show on Spotify. Don't forget to leave us a rating!

Keep being amazing! Bye! πŸ‘‹πŸ™‚

Meta

Title

TODO

Description

TODO

Show notes

<p></p>

<ul>
  <li><a href="https://datatracker.ietf.org/doc/html/rfc1983">RFC 1983: Internet Users' Glossary</li>
</ul>

<p>Have any feedback? Send us an email at <a href="mailto:[email protected]">[email protected]</a> or leave a voice message on <a href="https://anchor.fm/codeandbeyond">Anchor</a>.</p>

<p>
---<br>
<em>Music by Twisterium from <a href="https://pixabay.com/users/twisterium-20030970/">Pixabay</a>.</em>
</p>

Cloudless

Outline

Intro

Hello and welcome to a new episode of Code && Beyond. A podcast where we talk about software development and anything beyond that.

Cloud computing is part of our daily life for a long time already. Some products might not be even possible without it. Besides obvious things like apps on our laptops, smartphones, and PCs, there are cloud-connected TVs, refrigerators, keyboards and so on.

While cloud computing definitely provides many great benefits to consumers and developers, it comes with a certain price. This isn't just about money. For consumers there are questions like privacy and personal information, freedom of choice, necessity to be always connected. For developers it might mean increased complexity of the things they work on.

Today we aren't going to fanatically blame or defend cloud computing, but try to analyze what works and doesn't work for us personally, what alternatives we use and why. When it might make sense to go cloudless?

My name is Alex and as usual I'm joined by my good friend Pablo.

Highlights of the week

  • Alex: TODO
  • Pablo: TODO

Q/A

  • TODO
  • Summary

Outro

Okay! That's it for today. Thank you for listening! πŸ™‚

In case of any questions, simply send us an email at "codeandbeyond at protonmail.com". You will also find the address in the show notes.

If you are listening to our show on Spotify. Don't forget to leave us a rating!

Keep being amazing! Bye! πŸ‘‹πŸ™‚

Meta

Title

TODO

Show notes

TODO

Check other episodes of the podcast at <https://codeandbeyond.rocks/> and don't forget to give a rating on Spotify ;)

Have any feedback? Send us an email at <[email protected]>.

*Music by [Twisterium](https://pixabay.com/users/twisterium-20030970/) from Pixabay.*

Managing a technical product: the role of the PM in a development team

Outline

Intro

Hello and welcome to a new episode of Code && Beyond. A podcast where we talk about software development and anything beyond that.

Today I'm here with my friend Alex and a special guest: Robyn Farah. Welcome Robyn!

Robyn has been working as a pm (project manager) for more than X years so we have invited her today to talk a bit about her role and how pms can help to guide a technical product in the right direction.

But first of all Robyn, could you introduce yourself?

Highlights of the week

  • Alex: TODO
  • Pablo: TODO

Q/A

  • How would you describe the work of a project manager?
  • How do you balance stakeholders requirements and what your team can achieve?
  • How do you prioritize? Any tools/processes?
  • How to find the balance in the team: devs, qas. Specialist vs generalist
  • What are the abilities or skill you appreciate in developers?
  • And the ones you don't like?
  • What are your thoughts about tools and frameworks: example: Agile frameworks: Scrum, Kanban, etc. ?
  • Summary

Outro

  • (Good bye Robyn)

Okay! That's it for today. Thank you for listening! πŸ™‚

In case of any questions, simply send us an email at "codeandbeyond at protonmail.com". You will also find the address in the show notes.

If you are listening to our show on Spotify. Don't forget to leave us a rating!

Keep being amazing! Bye! πŸ‘‹πŸ™‚

Meta

Title

Managing a technical product: the role of a product manager in a development team

Show notes

This time Pablo and Alex are joined by a special guest: Robyn Farah.

Robyn has been working as a product manager for more than 5 years. So we have invited her to talk a bit about her role and how product managers can help to guide a technical team in the right direction. We are going to touch on topics of:

- using data to prioritize tasks and features,
- finding a common language between software engineers and managers,
- abbreviations and The Cooking Chicken Method.

---

Have any feedback? Send us an email at <[email protected]>.

Check other episodes of the podcast at <https://codeandbeyond.rocks/> and don't forget to give a rating on Spotify ;)

*Music by [penguinmusic](https://pixabay.com/users/penguinmusic-24940186) from [Pixabay](https://pixabay.com/music).*

Building an effective development environment

Outline

Intro

Hello and welcome to the new episode of Code && Beyond. A podcast where we talk about software development and anything beyond that.

As software engineers we rely a lot of tools. Editors, IDEs, linters, version control, terminal emulators, virtual machines, and so on. Tools we bought, downloaded for free from the internet, and built ourselves.

In some ways these tools define or at least affect quality of final results we produce. They boost our delivery speed and automate some boring tasks. Sometimes they drive us crazy, let's admit that as well πŸ˜„ We depend on them and need them every single day.

Let's talk about favorite tools and try to find a way to build the most effective development environment ever!

My name is Alex and as usual I'm joined by my good friend Pablo. Hi Pablo! πŸ˜„

We also have a special guest today. Juan Ibiapina. He has the most advanced development environment I've ever seen in my life :) Hello Juan!

Highlights of the week

  • Alex: Microsoft MakeCode.
  • Pablo: adventofcode.com
  • Juan: TODO

Special section

If you are listening to Code && Beyond on Spotify and like what we are doing. Let us know by leaving a rating on the show page πŸ˜„

Q/A

  • Introduction: Juan
  • Do we cover online tools or simply focus on the local stuff?
  • Juan's dev environment
  • What are our favorite tools?
  • What tools we built ourselves? Why?
  • How to measure effectiveness?
  • Developer experience or DX

Outro

Okay! That's it for today. Thank you for listening! πŸ™‚

In case of any questions, simply send us an email at "codeandbeyond at protonmail.com". You will also find the address in the show notes.

If you are listening to our show on Spotify. Don't forget to leave us a rating!

Keep being amazing! Bye! πŸ‘‹πŸ™‚

Meta

Title

Building an effective development environment

Description

As software engineers we rely a lot of tools. Editors, IDEs, linters, version control, terminal emulators, virtual machines, and so on. Tools we bought, downloaded for free from the internet, and built ourselves.

In some ways these tools define or at least affect quality of final results we produce. They boost our delivery speed and automate some boring tasks. Sometimes they drive us crazy, let's admit that as well :smile: We depend on them and need them every single day.

Let's talk about favorite tools and try to find a way to build the most effective development environment ever!

We also have a special guest this time. Juan Ibiapina. He built one the most advanced development environments :)

Show notes

<p>As software engineers we rely a lot of tools. Editors, IDEs, linters, version control, terminal emulators, virtual machines, and so on. Tools we bought, downloaded for free from the internet, and built ourselves.</p>
<p>In some ways these tools define or at least affect quality of final results we produce. They boost our delivery speed and automate some boring tasks. Sometimes they drive us crazy, let's admit that as well :smile: We depend on them and need them every single day.</p>
<p>Let's talk about favorite tools and try to find a way to build the most effective development environment ever!</p>
<p>We also have a special guest this time. <a href="https://github.com/juanibiapina">Juan Ibiapina</a>. He built one the most advanced development environments :)</p>
<p>
Notes:
</p>
<p>
- <a href="https://github.com/alacritty/alacritty">Alacritty</a> - a fast, cross-platform, OpenGL terminal emulator.<br>
- <a href="https://nixos.org/">NixOS</a> is based on Nix, a purely functional package management system.<br>
- <a href="https://github.com/junegunn/fzf">fzf</a> is a general-purpose command-line fuzzy finder.<br>
- <a href="https://github.com/juanibiapina/dotfiles/">Juan's dotfiles.</a><br>
- <a href="https://github.com/jose-elias-alvarez/null-ls.nvim">null-ls.nvim</a><br>
- <a href="https://starship.rs/">Starship</a> - the minimal, blazing-fast, and infinitely customizable prompt for any shell!
</p>
<p>Have any feedback? Send us an email at <a href="mailto:[email protected]">[email protected]</a> or leave a voice message on <a href="https://anchor.fm/codeandbeyond">Anchor</a>.</p>
<p>---<br>
<em>Music by Twisterium from </em><a href="https://pixabay.com/users/twisterium-20030970/"><em>Pixabay</em></a><em>.</em></p>

Working as a freelancer

Outline

Intro

Hello and welcome to the a new episode of Code && Beyond. A podcast where we talk about software development and anything beyond that.

For the last eight something years, I work as a full-time employee. But before that, it was many years of self-employment and freelancing. A wide range of experiences from amazing to not so much. But one this is true: I learned a lot.

The topic of today is freelancing.

My name is Alex and as usual I'm joined by my good friend Pablo. Hi Pablo! πŸ˜„

Highlights of the week

  • Alex: Hack && Tell.
    I had a chance to organize a Hack && Tell event and that was amazing experience! It was so inspiring that I would like to propose an episode on the topic of being a hacker. BTW, by the hacker I don't mean someone who breaks into computer systems, but someone who likes exploring and learning, who likes trying things out to understand how they work.
  • Pablo: TODO

Q/A

  • Cons and pros (for freelancer and employer)
  • Is that really freedom and independence?
  • One story from Pablo
  • One story from Alex
  • Summary

Outro

Okay! That's it for today. Thank you for listening! πŸ™‚

In case of any questions, simply send us an email at "codeandbeyond at protonmail.com". You will also find the address in the show notes.

Keep being amazing! Bye! πŸ‘‹πŸ™‚

Meta

Title

Working as a freelancer, consultant, full-time employee

Show notes

As software engineers, we aren't limited to just one type of employment. Some prefer to have more flexibility and jump from one project to another focusing on short-term tasks, others value stability and like staying with the company for a long time. We could work as freelancers, consultants, and, of course, full-time employees.

What's interesting, though, is that all these different types of employment have a couple myths around them.

In this episode of Code && Beyond, Pablo and Alex discuss some of the myths and are trying to prove or bust them using their personal experience.

Have any feedback? Send us an email at <[email protected]>.

---
Music by [Twisterium](https://pixabay.com/users/twisterium-20030970/) from Pixabay.

Problem solving

Outline

Intro

Hello and welcome to a new episode of Code && Beyond. A podcast where we talk about software development and anything beyond that.

As software engineers we are usually really good at solving problems. Well... at least software problems. Sometimes along the way we create even more problems which usually decided to solve later. We call that technical debt πŸ˜„

The topic of today is problem solving, and we are going to share our tips and tricks on that matter.

My name is Alex and as usual I'm joined by my good friend Pablo.

Highlights of the week

  • Alex: TODO
  • Pablo: TODO

Q/A

  • Time boxing
  • Scientific method
  • Research
  • Experimentation and prototyping
  • Diagrams or drawings on paper
  • Try to explain the problem in simple words
  • Try to think and describe the problem, not the solution
  • Summary

Outro

Okay! That's it for today. Thank you for listening! πŸ™‚

In case of any questions, simply send us an email at "codeandbeyond at protonmail.com". You will also find the address in the show notes.

If you are listening to our show on Spotify. Don't forget to leave us a rating!

Keep being amazing! Bye! πŸ‘‹πŸ™‚

Meta

Title

How to solve problems: advises based on our personal experience

Show notes

In this episode we share our tips and tricks related to problem solving. What and why works for us and maybe would work for you as well.

- Timeboxing
- The scientific method
- Experimentation and prototyping
- Diagrams or drawings on paper
- Try to explain the problem in simple words
- Try to think and describe the problem, not the solution
- ...and more

Check other episodes of the podcast at <https://codeandbeyond.rocks/> and don't forget to give a rating on Spotify ;)

Have any feedback? Send us an email at <[email protected]>.

---
Music by [Twisterium](https://pixabay.com/users/twisterium-20030970/) from Pixabay.

From geologist to software engineer

Outline

Intro

Hello and welcome to the a new episode of Code && Beyond. A podcast where we talk about software development and anything beyond that.
I'm Pablo and today I'm here with my friend Alex and a new special guest Pablo HernΓ‘ndez.

Quite frequently people ask me about how I got into software development, how difficult or easy it is to learn how to code, how hard it is to get your first job and so on. I come from a, lets call it, classic background: CS degree. That means my path to becoming a software developer was quite organic. That's why I thought that it would be great to have someone like Pablo who is coming from a totally different background.

Q/A

  • Can you tell us a bit about who you are and what you do?
  • What did you do before becoming a software developer?
  • When did you start to get interested in software development and why?
  • How does Geology relate to software development?
  • How difficult was the transition?
  • Where did you find the resources to learn or how did you learn?
  • Was it hard to land your first job?
  • How did you get it?
  • Do you have any tips for people who are trying to get into SF industry or change careers?
  • After you landed your first job, did you continue learning outside working hours?
  • I know that you also switch countries recently, how this impacted your career?

Outro

Okay! That's it for today. Thank you for listening! πŸ™‚

In case of any questions, simply send us an email at "codeandbeyond at protonmail.com". You will also find the address in the show notes.

Keep being amazing! Bye! πŸ‘‹πŸ™‚

Meta

Title

From rocks to code: How a geologist became a software developer

Description

This time Pablo and Alex welcome a new special guest, Pablo HernΓ‘ndez, who changed his career from a geologist to a software developer.

- What does it take to change your path? Is that a problem or an opportunity?
- Where and how to start your new career?
- How to find your first job on the new path?

Answers on these questions and more interesting topics covered in this amazing episode.

Show notes

<p>This time Pablo and Alex welcome a new special guest, Pablo HernΓ‘ndez, who changed his career from a geologist to a software developer.</p>

<ul>
<li>What does it take to change your path? Is that a problem or an opportunity?</li>
<li>Where and how to start your new career?</li>
<li>How to find your first job on the new path?</li>
</ul>

<p>Answers on these questions and more interesting topics covered in this amazing episode.</p>

<p>Have any feedback? Send us an email at <a href="mailto:[email protected]">[email protected]</a> or leave a voice message on <a href="https://anchor.fm/codeandbeyond">Anchor</a>.</p>

<p>
---<br>
<em>Music by Twisterium from <a href="https://pixabay.com/users/twisterium-20030970/">Pixabay</a>.</em>
</p>

Our ways to relax after work and recharge our batteries

Outline

Intro

Hello and welcome to a new episode of Code && Beyond. A podcast where we talk about software development and anything beyond that.

Yes, it's a long time since we did the last episode, but everything is fine. We are back on track with new ideas. That was just a summer break πŸ˜„

BTW, speaking of breaks, today we are going to talk about what we like to do after work to relax and recharge our batteries. Everything what works for us and why.

My name is Alex and as usual I'm joined by my good friend Pablo.

Highlights of the week

  • Alex: TODO
  • Pablo: TODO

Q/A

  • Pablo: Walk/Train the dog
  • Alex: working on side-projects and writing more software. (example: Q)
  • Pablo: Work in the field
  • Alex: handcrafting (example: concrete work)
  • Summary

Outro

Okay! That's it for today. Thank you for listening! πŸ™‚

In case of any questions, simply send us an email at "codeandbeyond at protonmail.com". You will also find the address in the show notes.

If you are listening to our show on Spotify. Don't forget to leave us a rating!

Keep being amazing! Bye! πŸ‘‹πŸ™‚

Meta

Title

Our ways to relax after work and recharge our batteries

Show notes

Yes, it's a long time since we did the last episode, but everything is fine. We are back on track with new ideas. That was just a summer break :)

BTW, speaking of breaks, today we are going to talk about what we like to do after work to relax and recharge our batteries. Everything what works for us and why.

Pablo will explain what is mantrailing and why he likes trees in his garden more than tomatoes. Alex will share why he likes to write software after writing software at work.

Links:

- [What is mantrailing?](https://www.mantrailinguk.com/post/what-is-mantrailing)
- [Fun with concrete](https://www.instructables.com/DIY-Concrete/). Just some ideas ;)
---

Have any feedback? Send us an email at <[email protected]>.

Check other episodes of the podcast at <https://codeandbeyond.rocks/> and don't forget to give a rating on Spotify ;)

*Music by [penguinmusic](https://pixabay.com/users/penguinmusic-24940186) from [Pixabay](https://pixabay.com/music).*

How to take on board new engineers?

Outline

Intro

Hello and welcome to a new episode of Code && Beyond. A podcast where we talk about software development and anything beyond that.

I'm Pablo and today I'm here with my friend Alex to talk about the onboarding process. We are not HR experts or anything like that but both of us have been onboarded in different companies and helped to onboard developers to the companies we worked for.

Highlights of the week

  • Alex: TODO
  • Pablo: TODO

Q/A

  • Let's start from the point of view of a new joiner. What are the things that you like to find when you join a company?

  • Let's switch to the buddy side. What are the things that you tend to do as a buddy?

  • Summary

Outro

Okay! That's it for today. Thank you for listening! πŸ™‚

In case of any questions, simply send us an email at "codeandbeyond at protonmail.com". You will also find the address in the show notes.

If you are listening to our show on Spotify. Don't forget to leave us a rating!

Keep being amazing! Bye! πŸ‘‹πŸ™‚

@startmindmap
' Side-notes:
'
' - Effort should be proportional the number of on-boarded people.
' - It's good to know the type of the on-boarded person. Some people prefer to work asynchronously and read documentation, others like pairing and human interaction.
' - Mention that buddies needs to be trained.

* On-boarding for engineeers
	* Check lists
		* General on-boarding
			* Company structure
			* Teams
			* Company values
			* Positions and titles
			* Payroll and holiday schemas
			* Company policies
			* Communication policies
		* Tech setup
			* Introduction into tools and services
				*_ Automate setup processes
				*_ Automate on/off-boarding in services
			* Introduction into engineering beost practices accepted in the company
		* Knowledge about the system
			* Business domain
				* Glossary
				* Workshops
			* Code base
				* READMEs in repositories
				* Pairing
	* Buddy system
		* Buddy checklist to make sure the on-boaring goes well
	* Feedback system about the on-boarding process
	* IDEA: Something to help with the imposter syndrome
@endmindmap

Mindmap

Meta

Title

How to onboard new software engineers?

Show notes

At Code && Beyond, we are not HR experts, far from that, but we have both been onboarded in different companies, as well as helped integrate new developers into the teams we have worked for.

In this episode of Code && Beyond, Pablo and Alex share their experiences with:

- onboarding buddy systems,
- discovering and acquiring knowledge in your new team,
- configuring your new development environment,
- conventions, consistency, and best practices.

Have any feedback? Send us an email at <[email protected]>.

---
Music by [Twisterium](https://pixabay.com/users/twisterium-20030970/) from Pixabay.

Code & Chess

Outline

Intro

Hello and welcome to a new episode of Code && Beyond. A podcast where we talk about software development and anything beyond that.

I'm Pablo and today I'm here with my friend Alex and a new special guest JosΓ© Doval (Pepe).

Pepe and I have been friends for a long time. We studied CS at the same university and even built a company together (not a very successful one). Back in the day, I used to think that he was a talented software developer who loved chess. These days, I'm not so sure anymore. I'm starting to think that he is a chess player who likes software development :-)

So Pepe, please introduce yourself and let's try to solve this mistery :-)

Q/A

  • Tell us a bit about yourself and your background.
  • Do you consider yourself a chess player who codes or the other way around?
  • Do you see any similarities between playing chess and coding? Anything that can be applied to both worlds?
  • Does the chess player mind help you in your software developer work?
  • Do you know how is the state of chess AI? is it used for training? competitions? etc.

Outro

Okay! That's it for today. Thank you for listening! πŸ™‚

Mention Pepe's Twitch channel?

In case of any questions, simply send us an email at "codeandbeyond at protonmail.com". You will also find the address in the show notes.

If you are listening to our show on Spotify. Don't forget to leave us a rating!

Keep being amazing! Bye! πŸ‘‹πŸ™‚

Meta

Title

Code & Chess

Description

This time Alex and Pablo welcome a new special guest, JosΓ© Doval (Pepe). Pepe is a chess player/teacher who writes code for a living.

In this episode of Code && Beyond we talk about machines playing chess, how chess skills could be applied in software engineering and beyond it.

Show notes

- Pepe Doval on Twitter, https://twitter.com/pepellou
- Pepe Doval on Twitch, https://www.twitch.tv/pepellou
- Pepe Doval on GitHub, https://github.com/pepellou
- Chessable,
  https://www.chessable.com/
- "How Life Imitates Chess" (book),
  https://en.wikipedia.org/wiki/How_Life_Imitates_Chess
- AlphaZero is a computer program developed by artificial intelligence research company DeepMind to master the games of chess, shogi and go.
  See https://en.wikipedia.org/wiki/AlphaZero
- MuZero is a computer program developed by artificial intelligence research company DeepMind to master games without knowing their rules.
  See https://en.wikipedia.org/wiki/MuZero.
- Correspondence chess is chess played by various forms of long-distance correspondence, traditionally through the postal system.
  See https://en.wikipedia.org/wiki/Correspondence_chess

Basher: a package manager for shell scripts

Outline

Intro

Hello and welcome to the a new episode of Code && Beyond. A podcast where we talk about software development and anything beyond that.

In the episode 29 we touched on the topic of building an effective development environment. Together with our special guest: Juan Ibiapina, we talked about our favourite tools and tried to define how we would build the most effective dev environment ever.

Today Juan joined us again to share the story of his Basher project. Basher is a popular package manager for shell scripts.

My name is Alex and as usual I'm joined by my good friend Pablo.

Hi Pablo! πŸ˜„
Hello Juan! πŸ˜„

Highlights of the week

  • Alex: TODO
  • Pablo: TODO
  • Juan: TODO

Special section

If you are listening to Code && Beyond on Spotify and like what we are doing. Let us know by leaving a rating on the show page πŸ˜„

Q/A

  • The original story
  • Design, architecture, conventions
    • Why you decided to use Bash script?
    • What lead to the idea of adhering to structures of existing projects instead of proposing some conventions and waiting for people to accept them? See.
  • Package directory. See.
  • Challenges of working open source
    • Does Bash script limit the amount of contributions?
    • How you deal with feature requests?
    • Burnout?..
  • Plans or ideas for the future
  • Summary

Outro

Okay! That's it for today. Thank you for listening! πŸ™‚

In case of any questions, simply send us an email at "codeandbeyond at protonmail.com". You will also find the address in the show notes.

If you are listening to our show on Spotify. Don't forget to leave us a rating!

Keep being amazing! Bye! πŸ‘‹πŸ™‚

Meta

Title

Basher

Description

TODO

Show notes

<p></p>

<ul>
  <li><a href=""></a></li>
</ul>

<p>Have any feedback? Send us an email at <a href="mailto:[email protected]">[email protected]</a> or leave a voice message on <a href="https://anchor.fm/codeandbeyond">Anchor</a>.</p>

<p>
---<br>
<em>Music by Twisterium from <a href="https://pixabay.com/users/twisterium-20030970/">Pixabay</a>.</em>
</p>

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.