578 karma · joined March 13, 2019
Industry: Satellite Imaging
Location: Germany, Munich (ONSITE/HYBRID)
Brief: Join a small team with a flat hierarchy to develop an API and GUI for selling high resolution satellite imagery!
Posting: https://www.linkedin.com/jobs/view/frontend-software-enginee...
Limitation: Nationality limited to EU member country, NATO member country, Australia, Japan, New Zealand, and Switzerland. We can help with the VISA.
"Page created 2003-08-23 and last revised 2005-07-31."
Page also has no sources of its own.
It primes the model with a list of known words/grammar and the A1/2 B1/2 C1/2 level of language ability.
I’d presume after each message you could get the model to dump to the config.
I haven’t work in this sector at all and am curious as to the limits of hacking it / working around the long term memory issues!
I have a nook in the geospatial field that helps narrow the competition but for the most part it’s been great.
I can see that mileage may vary depending on circumstance through.
Would have been a closer call if the CEO hadn’t died the year before…
https://register.classificationoffice.govt.nz/Pages/Screens/...
Albeit most of the entires under banned when searching without a filter are self explanatory.
It shows the git tree and includes a diff mechanism. Used it since 2019 after moving from TortoiseHg.
Demo Gif: https://github.com/mhutchie/vscode-git-graph/raw/master/reso...
Extension Page: https://marketplace.visualstudio.com/items?itemName=mhutchie...
Side note: does anyone know of a good tool / app for looking at things like that on iOS ?
I think mobilisation and moving toward declaring the special operation a war (more mobilisation) could be the beginnings of that slippery slope.
This is the current process that I think is fair and holistic:
1. meeting with the candidate, our manager, and some devs talking about their past exp., our company, our team, and their wants
2. Take home coding task based on our day to day work: This is linear with direct instructions for inputs and outputs; there is an optional part at the end for testing more tricky concepts. They are instructed to write clean and clear, no stress if they don’t finish, take their time with a week to do it (it’s a few hours work).
3. Interview with them walking through their code on their machine and describing their thought process, field questions from them if any are left.
Then we decide by a team discussion afterwards.
Gives them their space to think, reduced pressure for candidates who are socially pressured.
Thoughts?
I personally detest leet code as a recruiting tool.