it has quirks and limitations, some of which can be fixed by disabling system integrity protection but it can definitely handle window tiling and navigating with keybindings when you use the companion daemon https://github.com/koekeishiya/skhd
64 karma · joined May 19, 2011
hurshal#imap.cc
it has quirks and limitations, some of which can be fixed by disabling system integrity protection but it can definitely handle window tiling and navigating with keybindings when you use the companion daemon https://github.com/koekeishiya/skhd
it was beneficial for them because i was able to offboard and knowledge transfer much more effectively over a few months of part-time work as opposed to the standard 2 weeks notice.
it was beneficial for me because right out of the gate i had a consulting contract with a yc startup at a rate that was slightly higher than my yearly salary which i could use as social proof when reaching out to new clients and negotiating rates.
i ended up consulting for about a year as my only source of income where i took on a couple other clients through my network (ex-coworkers starting companies and needing help faster than they could hire, ex-coworkers referring me to others who were stating companies) and a few lucky connections through upwork (he contacted me on linkedin so upwork never got a cut of the invoices i sent). i've also tried toptal and moonlight but no contracts have come out of those platforms.
a year ago i took on a new full time job and i've been consulting on the side since. i agree with ananonymoususer in that i can have as much extra work as i can handle however i was lucky to have already created relationships with clients before getting a full time job. i'd imagine approaching a new client while maintaining a full time job is a harder sell than simply letting an existing client know that your availability will be reduced moving forward.
if i were any more skeptical it would underflow into unbridled hope.
the pro is that your async code explicitly defines points where context switching is okay since you're blocking on something anyways. this could be good for perf if context switching in the middle of a synchronous operation is expensive.
the con is that your async code might not cede control often enough to allow other coroutines to make progress.
so yes, you can have something hogging the runtime but in the context of an application that you control as a whole this is something you can avoid/fix if necessary.
at the OS level this might not make sense because you have to assume that applications are adversarial and will try to hog cpu time...
i think we've come far enough to agree that having playboy issues in your research lab is no longer acceptable so why continue to implicitly endorse that?
find a new picture if you want. it's not like this is the optimal image for testing anyways...
giving devs 4 year old laptops would help but when shiny startup is offering new macbooks how can you compete?
sorry to paint such a bleak picture but this stuff is ubiquitous, both online and offline, and it will eventually and consistently break your mental defenses in a way that you might not even notice.
i chalk that up to aws resources being backed by an eventually consistent db and the fact that aws has never built dashboards that are better than "acceptable".
it's possible that i'm missing something here but i've found terraform to be orders of magnitude better on both fronts. it takes a much more defensive stance on resource provisioning with retry logic and picking up on a previous `terraform apply` which timed out instead of rolling back the entire thing. and for whatever reason, terraform is usually way faster than cloudformation for provisioning the same resources.
shazam's value is obviously in how it scaled this method to millions of users and songs but implementing it for yourself on a limited catalog of songs is a couple days of work once you have the theory. in fact this was a lab project for the intro signal processing class at berkeley that i ta'd.
i'm not a fan of this kind of covert ad tech but i feel that this trend won't be slowing down any time soon...
seems like it would go nicely with a procedurally generated game too!
we used http://www.skulpt.org/ to run python in the browser. i resurrected the site to get some screenshots: https://imgur.com/a/xbpat
i would love to chat some more about your ideas, you can email me at hurshal.patel/berkeley/edu
one tool which i have built with my co-teachers in the past is a problem generator that tracks which concepts the user has "mastered" based on the number of problems they have solved for a given concept. we had a naive problem generator that used templated problem specs with randomly generated values: https://github.com/pftp/pftp-web/blob/master/practice/python... have you considered anything of the sort for students who want more practice?
working around HIPAA makes this an particularly hairy problem but from what i understand it is still possible to create a compliant solution for hospitals, emr vendors, and insurance companies, and even patients to detect medical fraud.
i couldn't find much but maybe some work is already being done in this space?
It is one of the classic CS textbooks still used by Berkeley (CS61A) and MIT (not sure) intro CS courses. Its not trivial stuff. While it wont teach you obscure data structures like ropes, it will expose you to a wide variety of topics including but not limited to: functional programming, lambda calculus, OOP, logic programming, client/server programming, non deterministic programming, streams as data, the meta-circular evaluator, lazy evaluation, and concurrency. I had a fairly strong CS background before taking CS61A at Berkeley, but this book (thanks to Scheme) taught me how beautiful computer science can be. Now working in Java is a complete turn off ;)