While all languages have their own strengths I would recommend Rust. I’ve dabbled in multiple languages over the last few years to broaden my horizons and Rust is for many reasons my favorite.
Biggest reason is probably the way the language invites tests to be written, almost making them unavoidable.
Nobou has created some of the best music I’ve heard. Favorite track though is still ”Under the Rotting Pizza” from the FF7 slums. I listen to his music almost daily, great composer.
This looks pretty nice, seems you’ve put alot of work into this. A suggestion, if you haven’t already the following things could really help for software development tesms:
* Ability to connect issues with branches on github/bitbucket etc. (so you easily see, and quickly navigate to, related code submissions). We mostly use JIRA and this is a crucial feature for our project management.
* Ability to set a category/group for your tasks, and in these categories specify additional fields (just simple text/drop-down/radio button fields). Projects often have individual needs, and cluttered forms is a nightmare.
* Time tracking on issues.
* Parent issues which tracks the collective time spent on child tasks, to get an overview of time spent on pieces of a project.
If you can make a simple enough interface I think this product may be viable, even if the market is a bit saturated. JIRA for instance has a horrible interface, even making minor changes is a dreadful experience. Almost cost me a keyboard and screen last time I had to modify what fields should be available for a particular project.
This is well written and reflects my own ideals quite well. Especially the part about all code being a liability.
We should always take a few moments to reflect before we write anything at all. Everything unnecessary we add is just another point of failure or potential security hole.
I constantly try to improve how I write my code. The last couple of years I’ve been involved in a couple of projects that’s required rebuilding a few times over because the project managers kept changing directions and was always in a hurry.
For one project I eventually managed to convince them to let our team write a more general purpose library to conserve time in the future. And this has paid itself of several times over.
When we write code it’s important we do consider how it may be utilised in the future. Since we cannot make exact predictions it’s better to make methods as small as possible instead to reduce the amount of time spent on refactoring (since this is unavoidable). This also helps us to create solid, more future proof, tests for our business logic.
You don’t need to follow a strict set of design rules, but general guidelines is a good idea. Like trying to follow SRP, avoiding more than x nubmer of lines for your method bodies and trying to avoid nestled code.
> Since we cannot make exact predictions it’s better to make methods as small as possible instead
No, please don't. Separate your functions based on what they're doing, not an arbitrary line count. If it takes 50 lines to do what's necessary, a 50 line function is absolutely fine.
You know what isn't fine? One operation split into 50 different subroutines that are all useless on their own unless composed together in order.
I agree with you, I didn’t say that quite right. In my mind this is actually pretty much what I meant, though I completely see how it can be misinterpreted. Line counts, like most other design rules should really be more like guidelines. Thank you for helping me clarify myself mate!
It’s refreshing to see a young person with such sound reflections about social media.
This post made me reminisce about learning web development when I was 11. Finding resources online was tricky, especially since I didn’t always have access to the Internet. I got books from my parents, and not very good ones either, but I loved them all the same.
I miss those days, when everything was more of an adventure.
I’ve been thinking about learning more languages over the years and your approach intrigues me. From the website it appears to be text based learning only though, is that accurate or does the app support vocal conversations as well?
Thank you, mate. Because it is in an early stage, it is based on text conversations aka chats for now. Vocal conversations is something I am definitely interested in & might explore soon.
This past year I’ve been trying to listen to my gut feeling more often and found that more of my endeavours are successfull, and very often when I disregard it, whatever I set out to accomplish will fail or have unforseen consequences. Funny, since there is no apparent logic to it.
Biggest reason is probably the way the language invites tests to be written, almost making them unavoidable.