111–120 of 326 posts
Try functtional programming using ramda.js to step up your js skills; try putting up a prom & grafana stack for monitoring, try using something like django & drf for your APIs (django is somewhat a large web dev market & is really solid, DRF will make you go lighting speed on your dev, it will also step up your permissions programming skills) ; work up to 100% coverage with unit tests and then write e2e tests that re…
Earlier quoted context omitted.
You should learn C. Life is too short to struggle with C++ now that we have better alternatives such as Rust. You can also ignore the people who ignore the complexity of web apps. Classic C programs are very often much simpler than full web apps IMHO.
Modern C++ is fairly easy to learn. At-least easier than either Rust or C.
https://en.cppreference.com/w/cpp/types/remove_extent https://en.cppreference.com/w/cpp/memory/shared_ptr https://en.cppreference.com/w/cpp/memory/polymorphic_allocat...
I think the basics that are similar to other languages (data types, basic pointers, basic references, classes and OOP) are indeed easy to learn as they are basically the same in most programming languages, but the more specific memory management and weird syntax around some standard libraries make it harder to learn, use and read. Let's be hoest, correct C++ code usually looks ugly and verbose.
Earlier quoted context omitted.
100% self-taught here. I change $150/hr for full stack Rails work and none of my clients have batted an eye at that. I’m thinking about raising my rates, actually. If you know what you’re doing, I can assure you, making money is not going to be one if your problems.
I have been trying to do this, and my biggest problem seems to be actually finding clients. After exhausting my social circle asking for work, it seems really hard to land a client. I am not even able to get anyone on the phone, and all emails are ignored. Any suggestions?
How is your knowledge of regular expressions? Spending a few days to learn them well² is really worth it. -- ² it's also worthwhile to know how they are working under the hood if you want to write high-performance regular expressions
^^^^ I'm not a dev, but regex is so much better when you understand what it's doing (I'm not claiming that knowledge in full!) The Book: http://regex.info/book.html I bought an older edition for a lower price, got through 7 or 8 chapters, and never touched it again- and I STILL gained huge amounts of knowledge and am much better at regex than I ever thought I'd be. Highly recommended!
I found that learning and writing some Clojure and Go made me think better about the code I was writing in my main language (python). I enjoyed working through Clojure for the brave and true: https://www.braveclojure.com/clojure-for-the-brave-and-true/ and the go tour is probably the best introduction I've ever had to a language: https://tour.golang.org/welcome/1
You can work through SICP to help learn Clojure/LISP at the fundamentals level, and then expand out to more practical use cases with the recommendations above.
Also, Jupyter Notebook is really cool, and it would be awesome to have Web Assembly versions that work in the browser. Colab is a nice UX, Binder, Thebelab, all steps in the right direction. Feels like notebook computing with WASM is under explored key infra for AI
How about getting back to the basics? You know, taking some maths classes, CS fundamentals, algorithms, data structures, that kind of stuff. It is timeless, and if you are self-taught, I can guarantee you that you have massive holes in your knowledge. Also, might sound off topic, but learning a new language (not programming, human) could be an amazing step forward, in ways you cannot even imagine now.
> and if you are self-taught, I can guarantee you that you have massive holes in your knowledge Just curious, why is being self taught a guarantee for having massive holes ? Can you give some likely examples ?
My personal drive for self-teaching generally stems from either a specific problem I’m trying to solve on a project or a desire to dig deep into something “cool” I’ve come across.
In the first case, I’m tugging on the strings that seem most likely to get me to the solution to the problem I’m trying to solve. There’s a bit of backtracking here and there as I choose dead end paths, but it’s usually a depth first traversal. I’m not trying to learn all of a field, I’m just looking at what I need to know to move past the hurdle I’ve encountered.
In the second case, the goal is different but the process is pretty similar. When I’m learning for fun there is usually a bit more breadth, since I’m not trying to solve a specific problem in the immediate future, but I’m also probably not building a robust implementation of anything. I’ll usually end up with a decent surface level understanding of a topic; this is useful in that, if I encounter a related problem in my work, I’ve got at least the concept in my mental toolbox already and can do a deep dive more easily.
Over time I’ve built up a pretty wide and deep understanding of a lot of things as I’ve built them, but I am also fully aware there a ton of gaps (and have a big topic list that I occasionally visit during a slow period).
Entrepreneurship? Getting more technical has a diminishing ROI after 10 years. Or something completely orthogonal to computing. Something you enjoy. For fun.
I disagree on this. A senior developer in any language will make far more, 2x-3x, what a junior developer will make.
Earlier quoted context omitted.
i'm a mobile application developer aspiring to learn backend. will this be a good read for me if i have negligible experience on server side of things?
Not really in my opinion, the book is really about the data aspect. Probably your best bet is to just pick your favourite programming language and build something in it. The book is great but not what you seem to be looking for.