71–80 of 88 posts
Scales wonderfully.
Scaling backend data structures is a difficulty itself and potentially different for every problem.
You’ll have more success (and fun) doing things where you can leverage your creative skill alongside your code learnings.
One source of deep admiration for many Ruby programmers was the artist/coder “Why the Lucky Stiff”. They created digital works of art that were a serious of small coding projects most of them fun, a couple highly useful.
The seminal book “Why’s Poignant Guide to Ruby” (http://poignant.guide) is still a beautiful read. Pair it with the website Try Ruby (https://try.ruby-lang.org) and you can plug in the examples from the poignant guide as you read along.
I’d recommend learning Hotwire and Rails 7 and then making small Rails apps to create small artistically interesting sites.
Ruby and Rails is highly attractive to people who value asthetics and beauty, and helps you integrate your creative impulses with how you code. Most languages don’t account for or attempt to address beauty in how you code. It’s by no means necessary but has been delightful for me finding a language and community that often highly values deep inner creativity along side coding principals.
Earlier quoted context omitted.
This sounds like good advice. Don't worry about Containers, deployment or testing "best practices" until you really need it. You'd be surprised at how many software companies' testing is "clicking around in the app", deployment is "upload to store/ rsync to server" and containers aren't used at all. Start learning React (you can also take a look at Vue), do some tutorials and build some CRUD app which has a database.…
You'd be surprised at how many software companies' testing is "clicking around in the app", deployment is "upload to store/ rsync to server" and containers aren't used at all. Not only that - a non-dockerized, bare-metal, but otherwise cleanly coded "rsync to server" app can be -- compared to the usual non-spec'd, undocumented cluster-f hairball shoved into a container, with a shiny layer of CICD thrown on top -- can…
But it helps to have an idea on how they work.
Earlier quoted context omitted.
Practice algorithms and read about software design in your spare time. Apply to tons of companies, be prepared to be rejected from almost all of them, and to be asked questions that you have no intelligent answer to. Remember what they asked you, learn the problems you got wrong, and repeat. It may be brutal and embarrassing at times but if you keep at it you will eventually get a job. The only thing I can say about…
the leetcode/algo question stuff is mentioned here on HN alot but I've never gotten to the point where a test was actually offered to me. will start practicing though and hopefully an opportunity pops up.
Earlier quoted context omitted.
i don't have any public facing repos, so i'll clean some up and try to emphasize that a bit more. in terms of interviewing, no opportunities so no experience. in the past ive had to apply to roughly 80 jobs to get one interview. recruiters on linkedin are a little better at ~30 conversations per interview but its plain exhausting, takes a ton of time, they demand replies instantly or ghost, but really its overwhelmin…
Having something that stands out on the resume will go a long way for you. A nice looking GitHub profile with some pinned repos with activity and a nice readme is what I would recommend. You can also find an existing project and contribute to it. What's your GitHub username? I can follow you
Earlier quoted context omitted.
how does one simply “get hired” while being mid career with no professional sw experience? asking for a friend.
incorporate your software company list a couple clients if you can point out that you’ve been working for that (your) software company for several years as a senior software engineer pass bullshit brainteaser problems viola
The Passionate Programmer (2nd edition) Creating a Remarkable Career in Software Development by Chad Fowler https://pragprog.com/titles/cfcar2/the-passionate-programmer...
You can check it out before buying at either of the following:
https://www.pdfdrive.com/search?q=chad+fowler&pagecount=&pub... OR https://u1lib.org/s/chad%20fowler