685 karma · joined January 25, 2017
Other than that meta-remark, you can take a look at how the cost and delay estimates evolve after a deadline is missed. Projects slip, but usually each missed deadline gives more visibility into the actual delivery date. If the updated budgets/plannings don’t converge, then this means the underlying project hypothèses are false (e.g. the technical complexity was completely underestimated, or the marketing target is moving faster than the project).
-rich formatting. It’s easier to scroll through your notes if the headings and sub-headings stand out. Also, automatic bullet lists with multiple indentation (I do a lot of these)
- ability to add pictures / screenshots. Comes in handy if you’re taking notes in class and you have the slides or pdf at hand. You can add a tricky diagram right into the notes, and draw over it if necessary.
- small timesavers, like the ability to mark a line as a to-do item (Ctrl+1 for One Note on Windows); you can then filter according to the to-do tag. This effectively gives you a centralized to-do list which you add to from whatever you’re currently working on without switching context. Or if you write an operation (e.g. “1+5-2”) and add “=“ One Note will compute that for you. Saves you the hassle of switching to another app. Or hitting tab to create a (rudimentary) table.
I also use mind mapping tools when trying to organize a large topic and I’m more interested in the overall picture than the details. I find that a mind-map/tree-like outline + notes or specific documents for the leaves or subtrees works well for me.
- look at the size of the inputs, it usually tells me what type of complexity my solution should have: if n is around 1000 I’ll be looking at O(n2) algorithms, if n is around 1000000 then it’s O(n) or O(nlog n), if n is 10*12 you need O(log n) or O(sqrt n). Knowing the complexity class gives you some idea of which algorithms to try or to discard. (And if you can get away with letting your naive solution run for a few hours to get the answer)
- figure out an inefficient solution that works for small inputs, then run it for a range of inputs and try to pick up a pattern (this is usually a last-ditch effort though).
- leave the problem alone for a while if I’m stuck on it for too long. This is usually a sign that I’ve taken the wrong approach; looking at the problem with fresh eyes will sometimes reveal a new way to attack it.
- read the PE forums for solved problems. These are a goldmine for mathematical analyses, code snippets, etc. Not to mention that some hard problems are related to earlier, easier problems and trawling the easier problems’ forums can land you the solution to the harder ones.
- try to frame the problem in a different way. Some PE problems are well-known math or CS problems in new clothes. For me this involves a lot of formula writing: I frame the problem in a mathematical manner and try to rearrange the terms into another formulation of the problem. Also lots of googling and reading Wikipedia articles about mathematical branches and theorems. Even if it doesn’t help for the problem at hand, it might help on a problem further down the line.
To clarify, the fine is due to the consent mechanism in Android. The fact that the action was led by the French regulator rather than the Irish one is due to this technicality and others (no DPO in Google Ireland for instance)
As a business, under GDPR I am responsible for the compliance of my subcontractors (which includes Google Cloud or Azure for instance). I read about this Google blunder and I think that I have other sh*t to worry about than how Google is screwing around with my data. On the other hand, Microsoft has demonstrated time and again that they care about their customers’ data. 2 examples: the fight with the DoJ over access to emails stored in Ireland and the fact they subcontract Azure’s operations in Germany to a German company (to avoid having to hand over the keys to the data center to a 3-letter agency: they literally don’t have them).
But there are other cases you should cover against, like the techie getting run over by a bus. The first thing that comes to mind is to make sure you have an admin account and/or a recovery procedure (a master password printed on a piece of paper in a safe, access to the account’s email address to reset the password, etc.) for everything.
Everything in this case is at the very least: AWS account (including the root account to manage the bills), e-mail provider, Gsuite admin rights, whoever you brought your domain names from, Dropbox, bank/PayPal/Stripe, GitHub/BitBucket, your telco, the admin accounts on your corporate PCs, and just about all the services you use on a daily basis. The email accounts and DNS are IMO the most critical; you can retrieve a lot of stuff if you control the e-mail or the domain name. BUT this assumes the accounts were set up with a corporate email, which may not be the case if you’re a small company - probably a personal e-mail was used to register the first services, which are also the most crucial. And if the techie knows what she’s doing, she will have enabled MFA, so e-mail alone probably won’t cut it.
Just ask yourself: if the tech person dropped off the face of the earth, what would you be locked out of?
I’ve recently seen secret manager and I first thought it was a rebranding of SSM PS. A quick google search seems to indicate that this is more or less the case at the moment, but the service will probably pick up new features as it matures.
For each position in the candidate's resume (or the last 3 if the resume is too long) I ask "what did you like about the job? what did you dislike? What made you happy to go to work and what made you drag your feet? It can be anything: boss, coworkers, how work was organized, office politics or lack thereof, visibility/interest of the job, commute time, offices... There are no wrong answers". Then I let them talk.
When it's done right, I find this is a great way to understand what motivates them and to make sure their intrinsic motivation is aligned with the position they're applying for and the company context. For instance, for a developer I'll be interested in someone who likes fixing problems; for a project manager, being result-oriented is usually a good thing. Someone who likes having a clear set of steps to follow is probably not a good match for my management style. Another thing that I can check is how they coped with a situation they disliked. Did they try to address it, work around it, or did they give up/avoid it?
I was first exposed to this approach as a candidate. I remember spending 90 minutes talking about all my previous positions, reflecting about what I'd liked and disliked for each of them, and coming out of there knowing more about myself than I did going in.
When hiring for an intern/junior position, I will often ask for a sample of a candidate's school projects. My rationale for this request is to see an example of their code. In practice, some candidates never follow up on my request; some send me a big hairy zip file with no context; and some obviously take the time to clean up their code and add comments before sending it to me. I've even had one or two create a GitHub account and push their code to a public repo to share with me, after we've gotten to talk about their knowledge of git.
Thank you for the insight that while trying to gauge technical skill I ended up evaluating thoroughness and care ;)
For messaging, one could argue that it already exists: Signal (which has already benefited from FB’s announcement that they collect WhatsApp)
I know that the latter will probably be something really interesting or even awe-inspiring that doesn’t leave much to be discussed. While the former is (sometimes) a sign that the comment section will be more interesting than the article. At the very least I can expect different, well-argued viewpoints, and reading a thoughtful argument is something I enjoy.
Re junior positions, they’re often not the most interesting jobs, unless you have a specific interest in learning the ropes (or you love fixing bugs and handling JIRA tickets ;) - hence my remark.
A final thought: if working remotely is on the table, i.e. if you’re not explicitely looking for a local job and the accompanying social interactions, maybe you can look at working remotely for a US company. Hit the latest “who’s hiring” post, look at remote job postings that sound interesting, and contact the recruiter to see if your profile could interest them and if not what you would need (degree, portfolio, previous experience) before applying again.
So I would suggest looking at the question from this angle. What excites/motivates you enough to invest some time in it? What kind of job or context do you see yourself working in? If you are academically oriented, getting a degree will probably bring you the most satisfaction while you figure out the next step. If you’re more practically minded, I would suggest building your own one-man business, capitalizing on your interests and expertise (ML to automate lawyery stuff?)
Given your past experience, I don’t know what you would learn in a bootcamp and (in my opinion) a bootcamp on your resume has weak signaling power. I would suggest looking at apprenticeship degrees, where you’re at school part-time and work the rest of the time. They’re pretty common (in France at least) and some of them are explicitely targeted at people who already have had a first non-IT career. The upside is that you’ll get to work early on (these schools will usually help you find a company). The downside is that you’ll be working in a junior position. But, aside from starting your own business, I don’t see how you can avoid that.
FWIW, in my company we have an apprentice data scientist who used to be the GM of an industrial company in Asia! He caught the data science bug a few years back and he’s having a blast going back to school and learning on the job.
IIRC this strategy was tested by Jay-Z with little success. Taylor Swift also came back to Spotify...
Funny story (but not the ah-ah funny kind): such a service (hosting different customers on the same Windows machine) was still running in my previous company as of 4-5 years ago. They had long moved from physical hosts to VM, but were stuck with the legacy CMS/control panel which was more or less unpatchable (as in, the software editor didn’t exist anymore). About once a week, one of the host VMs would be taken over by hackers using one exploit or another. In that case they would kill the VM, boot a fresh one from a clean image, and start serving the customer data again after making sure it was clean. The service was not sold anymore but they had long-running customer contracts. It wasn’t making enough money to justify rebuilding it with modern software, but it was making enough that simply killing it wasn’t an option.
The problem is that everyone notices the terrible UIs, but really good interfaces get out of your way so you don’t always notice how good they are. Hence a lack of recognition for good front-end devs.