During my PhD in Data Science at Stanford, I got sick and tired of ghost jobs & 3rd party offshore agencies on LinkedIn & Indeed. So I wrote a script that fetches jobs from 30k+ company websites' career pages and uses GPT4o-mini to extract relevant information (ex salary, remote, etc.) from job descriptions. You can use it here: (HiringCafe). Here is a filter for Data science jobs
| #!/usr/bin/env python3 | |
| import sys | |
| import io | |
| import zipfile | |
| import tempfile | |
| from pathlib import Path | |
| import sqlite3 | |
| import json | |
| import shutil |
this is a rough draft and may be updated with more examples
GitHub was kind enough to grant me swift access to the Copilot test phase despite me @'ing them several hundred times about ICE. I would like to examine it not in terms of productivity, but security. How risky is it to allow an AI to write some or all of your code?
Ultimately, a human being must take responsibility for every line of code that is committed. AI should not be used for "responsibility washing." However, Copilot is a tool, and workers need their tools to be reliable. A carpenter doesn't have to
| import React, { useReducer, useEffect, useRef } from 'react'; | |
| import firebase from 'firebase/app'; | |
| import equal from 'deep-equal'; | |
| function filterKeys(raw, allowed) { | |
| if (!raw) { | |
| return raw; | |
| } | |
| let s = new Set(allowed); | |
| return Object.keys(raw) |
| function main { | |
| Update-Windows-Configuration | |
| Install-Utils | |
| Install-Browsers | |
| Install-Fonts |
| #!/bin/sh | |
| # SPDX-FileCopyrightText: 2017-2024 SanderTheDragon <[email protected]> | |
| # | |
| # SPDX-License-Identifier: MIT | |
| arch=$(dpkg --print-architecture) | |
| echo "Detected architecture: $arch" | |
| case "$arch" in |
| using UnityEngine; | |
| using UnityEditor; | |
| using System.Linq; | |
| /// This just exposes the Sorting Layer / Order in MeshRenderer since it's there | |
| /// but not displayed in the inspector. Getting MeshRenderer to render in front | |
| /// of a SpriteRenderer is pretty hard without this. | |
| [CustomEditor(typeof(MeshRenderer))] | |
| public class MeshRendererSortingEditor : Editor | |
| { |
| /* | |
| This is a minimal working example | |
| */ | |
| import React, { Component } from 'react'; | |
| import Filters from './Filters'; | |
| import InputFilter from './InputFilter'; | |
| import allMovies from './movies'; | |
| class App extends Component { |
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
- Follow standard conventions.
- Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
- Boy scout rule. Leave the campground cleaner than you found it.
- Always find root cause. Always look for the root cause of a problem.