Good riddance. A thinly veiled power grab to make the web a walled garden. Now lets do the obvious thing and just do preferential treatment for fast loading pages.
This! I got this feature enabled, it works fine, why remove it. How much dev work is saved by removing a compact view? Mozilla is straying further and further from the open source icon it was, death by management....
Yet Linux is way more popular option both on the server and the desktop. Way way way more people and companies contribute. And it seems that BSD use is declining on servers? [1] MacOs is a unix but how does that help the BSD community, as most code is build upon it and the changes don't really trickle back. Companies just take, if you can do whatever you want with the code. You can wish that everybody shared back in a perfect world, reality proves this is simply not true. At least the company trying to influence development has to contribute to gain influence, and you can fork it (with their changes!) if you don't like that.
The GNU license at least somewhat protective. To each their own, but I would never release software under a permissive free license.
Yes the compromise is worth it. These are the best SoCs available on the open market. If we aspire to more open and repairable devices then we need to start somewhere, and we have to put our money where our mouth is. If volume goes up we get better open products. Luckily Pine64 is doing really well so much so that non geeks are buying their products (with all the software support problems that come with them)
I bought a pinebook pro and i have some SBCs. The PBP is perfect travel laptop with long battery life that can run on my phone charger. Firefox runs buttery smooth on Manjaro i3.
Very happy with my pinebook pro and rockpro. The pinebook pro has amazing build quality and usability for the price. When my oneplus dies hopefully there will be a pinephone 2!
I' m not in the US, so no crazy salaries on both sides. The average doctor probably makes more but the best programmer makes way more than the best doctor. However with long hours, night shifts, pressure etc you have to enjoy what you do or burn out early.
Not really. Picked it up as a child, loved programming and tinkering. Had to choose between computer science and medicine. There are actually lots of things in common, debugging complex systems, building a mental model, abstraction, looking up solutions based on certain hints. Orthopedics is a highly technical field, working with implants, computer surgery, imaging and such so its very useful. Programming trains your problem solving abilities.
I really believe everybody should have the opportunity to learn to code.
Not really a startup in the sense of a VC backed multi million dollar company but three working friends and me have bootstrapped a fitness websites with science based health advice, mostly free, to basically the largest fitness related website in the Netherlands. Currently employing people, which i think still sounds insane for a hobby project. https://www.fit.nl. 700.000 pageviews a month. App, 2 books, system for training and meal schedules etc. One now works full time as a lead/writer.
As a day job I'm a full time resident of orthopedic surgery. Busy days. I've done most of the programming of the website (custom theme on wordpress), product comparison engine and other custom pages. And server admin for discourse, mattermost etc
Some important findings:
- You have to care otherwise it becomes a chore. In this case it keeps people healthy. We give free advice that i think is pretty good, e.g on the forum, I love that part. The link with the day job is here. Lots of stuff i tell people during clinic hours applies here as well
- As its completely different it still feels like a hobby. Learning to do stuff is fun
- Clear separation of responsibility, do stuff you are efficient in
- A ticketing system for jobs, pick up stuff when you have time. Anybody can add to the ticket list but the list owner decides what comes first.
- Keeping the tickets bite sized. GIT to deploy, deploy often
- A time tracking system (Toggle) tracks time spent.
- Mattermost for private discussions and planning
- Meetups and fun activities to keep the group focused
- Managed main server (websynthesis) in case the website goes down and the other technical guy or me are unavailable. More expensive but less stress this way.
Written in Go, its lightweight (runs on my beaglebone and pi's) and has been absolutely stable for me for years (100 GB, 10+ devices). It hits all the requirement except encrypted nodes.
2nd year Surgical resident, part of my education to be an orthopedic surgeon. Currently working in a town 100km away.
05:45 wake up, quick breakfast and cycle to the train station
06:20 train. Grab the laptop, prepare for procedures or work on research
07:45 handover or
08:00 start of first procedure. Do timeout, grab a coffee while the anesthesist does his job
12:00 when lucky time for lunch behind the PC, administration
16:30 usually last procedure, handoff when on wards or clinic duty
17:00 see patients of the day, check for question from the new shift of nurses
18:00 train home. Do some coding for a company my friends and me run
19:15-19:30 home
Excerise, work on scientific papers or meet with the team at the office. Work on some points in the job queue. Sleep at 23:00.
Just a few more months and I'll change to a job closer by
Great alternative to ampache etc, very slick interface.
The hardest part is keeping music and especially playlists synced between devices, something that can be solved with syncthing or similar software. Playlists are very hard though with offline desktop clients (Musicbee)
These articles are always way overhyped. A lot more development is needed before it can even be safely used as a tool alongside radiologists. The dermatology example is an excellent one. It would be great to have a simple image classifier that can help the diagnosis before the clinical appointment.
Software on its own can't even tackle a 'simple' task as reliable 6 lead EKG (electric heart film) analysis yet. A chest x-ray has a lot more variables. Plus clinical variables as patient history etc can make a big difference in diagnosis on a similar image.
Very interesting article, his previous book 'The emperor of all maladies' is also highly recommended. A lot of medicine is not level III evidence or better backed.
As both a doctor (surgical attending) and programmer medicine feels not just like debugging a very complex non linear machine. Patient psychology is one of the hardest parts of the job. Is the stomach pain caused by a psychical problem or can it be functional?
The use of protocols (part of the science) can help in catching non typical presentations of illnesses, especially if the patient is not adequate in presentation (drunk, very young, old, trauma etc).
But sometimes medicine comes down to an art, when you have the feeling something does not add up, you have to dig. The same with (older) attendings with very attuned diagnostic skills due to lots of experience that can help solve non-obvious cases.
The Selfish Gene - Dawkins, The Red Queen - Ridley
I've read these books midway through high school, already interested in biology and medicine. The depth and complexity of how life forms handle evolutionary pressure is mind blowing. Why you favor relatives over strangers, the competition between mother and child, progress through collaboration of genes etc. You see the world completely differently (after reading many more books on geology, genetics, anthropology, anatomy, cellular biology etc) afterwards.
For a novel: Cryptonomicon by Neal Stephenson,
Truely changed how I look at computers and encryption as a not mathematically inclined reader. Building a computer out of church pipe organ components etc.
Yes, some standard procedures on ASA1 patiens do not require a lot of sophistication. However do not underestimate how hard anesthesiology is, while 90% routine, 10% is incredibly complex stressfull scenarios in trauma/emergency, surgical complications, adverse events. Its much more than just heart rate, RR, oxymetry etc. Its knowledge about medicine interactions, organ systems, physiological systems and the skill to perform under immense pressure (trying to provide a permanent airway through facial trauma or large bore IV access for fluid replacements on a patient in volumetric shock) And while uncommon it can happen during standard procedures in ASA1 patients. I'd rather have the anesthesiologist close please.
As a quick sedation system these sound wonderfull though, for example for resetting joint dislocations in the OR where all emergency staff and equipment is already in place.
Because your immune system, a highly complex interaction between countless cells, is not fully determined just by your genes or your environment. There is also a stochastic factor.
Underestimating own skill and especially judgement of a situation as a young employee. Fear of larger organisations, complex processes that leads to avoidance of these type of projects. I've gained confidence over the years, now its easy. But it has led to regrets about missed opportunities. Also, not starting earlier with a side-business.