Got a 17" Oryx pro last week. So using it with integrated Intel graphics, power saving on and screen brightness low, it's about 4.5 hours. I noticed if I adjust the screen brightness like even 10% it can add an extra 30 minutes. I'd assume it might be even longer for the smaller screen oryx versions. Now im wondering if there are a few other kernel governing tweaks that'd increase the time.
Minimum wage paid for human capital, inflating the cost of collecting attention/info sold by media companies. Reminds me a bit of brave and attention tokens. It feels like a comparison between libertarian policy and state policy.
Interesting idea, but who would pay a 12% tax for writing a blog post, or leaving a review. I think it would pass the costs onto the consumers, raising the barrier of entry to information liquidity.
From what I understood it uses RDF triples, linked data, and uses an ontology, that is compatible with Solid aka linking a "Person" to a "Wallet" and actions to a transaction/service/resource
"Common Crawl" and Elastic Search? Elastic Search for ipfs. Adding a few petabytes with a lot of bandwidth to ipfs, maybe modifying the warc/wat headers to support ipfs address pinning? Some extra web browser code to sanitize, token harvest, pipe webpages that users visit back into the indexing/pinning locally with metadata for times visited and other counts, with a ui that allows user to pick and choose what gets indexed. Some extras around front page click through thrashing because of poor results, incentivizing quality with upvotes/downvotes/flags, charging for search, and paying for it with resource (bandwidth/storage) commitments.
Was homeless when I went to a dev boot camp. Had no industry experience, just a bunch of python scripts to automate my old job, and a few years of linux usage from not liking windows. Focused really heavily on several SPA frameworks, and javascript/nodejs. The biggest help was the hiring network, whiteboarding practice, and resumé critiques. Also that I submitted like 5 applications per day to anything even partially related for a solid month. I never mentioned my dire straights, since there appears to be a social stigma in the industry, although there doesn't seem to be a stigma against the happily ever after finding work. If they ask why there's gaps in your work timeline, don't tell a sob story, just tell them it was health related and move along. Also try to schedule groups of interviews a few weeks out, it gives you very real leverage in the labor markets, instead of appearing/sounding desperate let them show their hand, since you're already surviving you dont need the job/career, if anything they need you, the labor markets are seriously strapped for talent, so take on some part time minimum wage work that you'd like, and take as much time finding the right fit team/culture/project that you would enjoy. Don't give up, never stop learning, you can do it.
Edit: imo, Also don't deal with recruiters they'll plug anything/anyone for a CTO position if they can pull the commission, although I guess maybe as a way to practice interviewing.
fwiw, I graduated with a degree in painting. Got into an ecommerce shop. Figured out how to automate my position. And felt a big draw to programming. Went back to school via a bootcamp and have been a "developer" for the last two years. Mostly CRUD but recently ML and the tools to shuffle data around to input into the ML. I have been in a slump lately, decided to pick up doing part time bicycle messenger/delivery work on the weekends and for an hour or two after a few times a week. There is something satisfying peddling items around the city for people. Tangible and visceral with immediate feedback. I've found it helpful, it has rebalanced my priorities in a sense. Being out in the world, as opposed to continuosly being in an abstract space all the time.
It took me about 7 weeks, in that time I submitted upward of 90 applications, as I was okay with moving. And had interviews/emails trickling in at the 2 week mark. My resume was groomed, and edited by some career development minded folks, I did a lot of reading on resume formatting and word choice. Practiced white boarding, reviewed and felt comfortable with the base data structures and algorithms.
I would say if you can speak to your relevant experiences and are able to tie that into the position, most times the 2-3 years of experience or BS in CS or engineering is a soft requirement.
That being said shoot for doing 4-5 applications per day, and if an interview goes poorly, brush it off, and get ready for the next one.
I created categories, or staging points for each application in asana, and treated the job search like work. (Applied, emailed, follow up thanks, phone screen, phone interview, onsite, etc)
Depending on who is doing the hiring the process could take an hour or it could take 3wks+ if its a big organization.
Edit:
Also reframe any "problems" as challenges, and instead of making negative comments try to pull out the positive from any given situation when asked about something.
https://wiki.ubuntu.com/FocalFossa/ReleaseNotes