I've been trying to think through something called Story-So-Far which is supposed to be an IDE plugin which logs user keystrokes with timestamps and saves it to a local file .ssf . This file should be replay-able in the IDE which essentially means other developers can literally see how the software was made by the original author. This aims to replace tutorials and also increase open source contributions once you see for yourself how the software was written. I know there are security risks involved. But one problem at a time. Haven't started on the actual implementation yet.
what do you look for in a candidate when hiring for a remote position ? I am 3 years experienced dev and cant even get my resume filtered for first round. I do have 3 months of remote Gsoc experience if that counts. But i am curious, is there some particular factor that gives an edge over other candidates ?
One of the benefits listed in the manifesto (and often touted elsewhere) is that you are not limited to a specific region when hiring.
Unfortunately, what this means for candidates is they may have to compete with a LOT more people.
Another challenge you're likely facing is that a lot of companies are only willing to hire senior developers to work remotely because hesitant upper management thinks they will be more trustworthy (completely ignoring the level of trust inherent in having someone write code for them when they themselves can't even verify it).
That negativity aside, here's some advice: As much as there is some backlash around the idea of a GitHub profile being mandatory, one VERY practical use of an open source portfolio of some kind is that almost all open source project work is done remotely using the very same skills required for successful remote employment. This applies even more so to non-programming contributions, in my opinion, which means you don't even need to contribute code to demonstrate these skills.
i guess because the consumers might not always be tech savvy. they just want those items/coins/rewards in whatever game/app they are playing/using. a minor pop-up about the mining stuff wouldnt bother them (although app perf might be affected). that's how i see it.
Been using re-frame in production since 2 months. Lost some hair in the first 3 days ( had to make some db structure decisions based on requirements) but after that it's been amazing and adding new features has become really trivial.
Not a bad intuition to have. But with some reading you can learn that "db" refers to the in-app, in memory (or local storage) database, which is designed to hold all your application state, which allows it to be clearly transacted against and referenced from anywhere in your app.
You start writing pure functions which take the current "app-db" as an argument, and return what the "app-db" should be. If React is `v=f(s)` (view is a function of state), re-frame is `s=f(s,e)` (state is a function of the previous state, and events)
You know nothing about software architecture if you think that you can't optimize a software performance/responsiveness changing the way you store/normalize/retrieve data.
I know that I wouldn't want the choice of a fly-by-night front-end framework influencing how that's done with a back-end database. But, looks like I made the wrong assumption about the db structure that was influenced, I guess we have front-end databases now, which is an interesting idea I will be exploring furtherer.
Silly question. Can I use this to interact with a machine learning model written in python from javascript on react native ? It'd be great if someone could point out the feasibility/limitations
Just trying to make gemini-cli work with my enterprise copilot subscription.