I worked on my own open source project-- without getting paid-- for months, just to have a complete project where I could show hiring engineers my code & a demo page about the project.
Two weeks after that, I was hired. I haven't lost the interest of 3rd party & in-house recruiters since then.
If you don't have a modern, up to date, open source project, as part of a web portfolio, you might consider putting 2-3 months into both a project (or set of projects) & a portfolio (or even 6 months like my crazy self did, while unemployed), then publish it.
You'll have a shiny new project, demonstrating modern skills, to show to a hiring manager/recruiter.
Obligatory: "But you're leaving out women's historical involvement!"
"The Women of Fly Tying
OKAY BOYS, GET OVER IT: women have made some of the most important contributions in the fine art of fly tying.
By a Thread: A Retrospective on Women and Fly Tying (The Whitefish Press), by Erin Block, is a celebration of the critical impact women have made on tying flies. Erin includes the work and stories of Dame Juliana Berners, Mary Orvis Marbury, Elizabeth Greig, Winnie Dette, Mary Dette Clark, Elsie Darbee, Helen Shaw, Megan Boyd, and Frances Stearns, along with modern tiers Sharon E. Wright (Sharon is a regular contributor to Fly Tyer magazine), Cathy Beck, and April Vokey.
Do you like a good mystery? Erin solves one by uncovering what ever happened to Sara Jane McBride, the famed fly tier who was also America’s first entomological fly angler.
Erin’s flies have appeared in Fly Tyer magazine, and we will have fuller coverage of her new book in a future issue of our magazine. In the meantime, congratulations to Erin for making such an important contribution to the literature on fly tying!
To buy a copy of By a Thread: A Retrospective on Women and Fly Tying, go to www.whitefishpress.com."
>Russia tested a satellite-to-satellite weapon which is completely unprecedented militarization of space.
No, it's not unprecedented.
Reality: The public is obviously not privy to the the 100% truth of geopolitical conflicts.
Based on what a source told me (son of a state department employee), US and China have both shot down each others satellites-- back around 2007 or 2008.
Back when the US claimed it was testing out the ability to shoot down its own satellite... Yep, that's what they told the public.
The reality? Let's just say it's a bit different from what the government releases to the public. ... as in... The US shot down a Chinese satellite after they shot down one of the US'.
No one can build your strategy for you-- you'll want one suited for you, and no one knows you better than yourself. Although I am sure certain folks can help: Life Coaches, Counselors, Psychologists, etc.
Find resources on:
- Skills that BOTH interest you, and are economically in demand
- Geographical areas where those skills have a competitive advantage and are in demand
[3] You can find entire libraries of skills at sites like Lynda.com and Udemy.com
I am an web app developer. No tech degree.
How? Built my skills. And strategically: I am creative, interested in business & entrepreneurship, interested in freedom, technology, and building things. And, I want to make good income so I can support a community where I help people grow.
Looking at those desires... it fits well with a Web App Developer career.
Likewise, you need to determine:
A. What do you want ("Goal". Not having a goal is like having a map without a destination: Going nowhere)
B. What you're willing to get what you want ("How badly do you _want_ to reach your goal? Do you really _want_ it? Again-- how badly? Are you willing to take 6 months off from work to grow your own skillset, full time, via project-based work, in order to leapfrog yourself into a new career?)
Just some ideas. It's not tough. Just ask a search engine the right questions. And know yourself.
Go through trials, tribulations, challenges-- One doesn't get to know their self by living an easy, meandering life. We get to know our self and what we're capable of by going through significant challenges-- By testing ourselves.
Awesome project. The only suggestion I'd have is organizing the code files.
The root folder is full of stuff-- from "helpers.js" to "permissions.js" to "index.js" to stuff about views and tests. If these aren't closely related, I'd personally set them into separate folders to organize main functionalities.
Also, I'd prefer to see route separated out of the index.js folder, personally. I'd keep index.js as minimal as possible-- just the main server config stuff.
I'd also remove the underscore prefix on the folder names, but that's only b/c I think most people use underscores unnecessarily.
Anyway, it's just minor stuff. It's awesome to see what you've built OP.
"Yes, I know we are "equal" but oh my goodness, look, this equal person did this equal thing!" ... yet this excitement implies lack of equality-- if equality was inherent, there would be no need to exclaim equality excitedly.
I'd recommend checking out nootropics, such as lion's mane. Also, nutrition & exercise (both mental and physical)-- If you don't use it, you'll lose it. And social well being.
I agree-- it feels 100% like tail chasing, and not like normal problems I encounter in coding up a business-tool related full stack application.
Plus, I have my own personal projects to work on. Plus, I have an open source project available for perusal. Therefore, I refuse to do leetcode/hacker rank problems for interviews.
I lucked out-- For my current job offer, I simply had a 45-minute conversation, answering technical questions about a particular language, as well as behavioral questions, with three people involved in the hiring decision. Two days later they notified me with a verbal offer that they would like to hire me. Note: I also have an open source project which they reviewed during their hiring of me.
So, given that success-- one interview -> hired, I am quite happy, but I know it's not the typical manner of hiring.
That said, since other recruiters are contacting me regularly, I am taking interviews. However, i inform them:
A. I am coding my own business project at the moment.
B. I do not code for free, not even for interviews.
C. I've received a verbal job offer, from an interview which did not require a coding test.
D. I have an open source project featuring a few thousand lines of code which can be reviewed-- if a hiring engineer is actually interested in seeing my code.
(That said, I did notice that learning to solve algorithm-efficient problems via video series has improved my skills. Just not that substantially, and not in a way that is necessary for my projects-- the code already works pretty gosh darn fast at the scale of my projects & past projects for companies which hired me-- they didn't need google or amazon level code efficiency.)
> "the mass die-offs we're seeing are because the world's coral reefs will be dead by 2050"
This does not make sense.
Let's break it down:
This is what you're saying:
"The [current thing happening] is due to [the occurrence of a future thing]."
Clearly, something in the present is not due a dependency on an event which has not happened yet.
What you should perhaps say is something more like:
"The [current thing happening] is due to [the same causality] as what will cause/is causing [the future occurrence]."