Quantum dot displays can, but they're a bit further out. Too bad there are colors that have no wave length because they're an artifact of our perception caused by combining real colors. 3 color pixels with N combinations is good enough for now, until we find something better.
More and more are going online every day. Remote learning is the hot new thing in education.
80% of what you learn in college is via interaction. During freshman orientation, they make it clear that their primary role as an educator is not to teach knowledge. The key to good answers are good questions, teaching you how to ask good questions is their goal. How many online classes teach you how to ask good questions? Very little time was actually spent as lectures.
I have $600/m in medical debt and that's with insurance that covered 90% of the costs, and with below average medical care costs compared to most of the USA. Throw in another $600/m for rent, another few hundred for food, I require a cellphone and internet access for work, 10% of income to 401k, $150/m for health insurance premium, another $100/m for car insurance.
I don't understand how you live on $750/m and talk like it's easy street. I live in a town with $30k being the median household income. It can be done, I've done it, but I was poor enough that debt collectors effectively gave up on me and wouldn't take me to court because I was too poor to waste their time trying to garnish my wages.
When I lived with my parents or a room mate, $750/m was like being a king.
You can't default on government backed student loans.
The millions of young people today, who collectively owe over $1 trillion in loans
50% of that $1 tril is owned by 10% of the students, and on average those students make less than a high school drop out. Sounds to me like for profit schools are preying on the stupid.
Time is money. Unless you are saying someone should be able to spend 10+ years on underwater basket weaving for free. I would like to play games all day to, but I know time is not free and someone has to pay for it.
Of course an Art degree does not mean what they learned is entirely useless, but what is the break even point for time spent learning something not directly marketable and value added to society as a whole? A masters in Philosophy sounds like a complete waste of tax payer money, but I could appreciate the argument for a BS in American history adding value because of a more educated populace for better voters.
At this point, if these basic things are still considered good for society, then make them part of high school. Why not just extend high school 4 more years until 22? It's a slippery slope.
I got my degree by first going to community college (dirt cheap) and then doing online classes at the cheapest state university to finish the bachelors.
For the good Universities around here, few credits transfer from Community Colleges to the University system. Few classes are online, especially high end classes, since most classes involve large amounts of team effort, class room discussions, or hands on work. The capstone project has always been a multi-person team effort where 60% of your grade came from your team mates.
There is a reason they have a 100% job placement post-graduation.
I don't actually use it, but I have read about it when researching scaling issues. From what I've read, calls do not have to be async, but it is the general convention for IO to be async.
in the eyes of executives your managers are ultimately responsible for the project's success or failure, regardless of who actually messed up. So they absolutely cannot just sit back and wait for developers to be done with their work and hope for the best.
Not always. Many of my projects are special requests by VPs and directors that are ASAP with no real deadline because it needs to be done yesterday or very important projects that need tight turn-arounds for nearly everything, like bug fixes and new features, live in prod.
When the normal process can take hours, I can take minutes. It's a trade off. They know I am a single point of failure and there is good reason to have a formal process for most things, but some times customers have outrageous demands and too many hands in the pot makes that impossible. So they throw me at the problem and I design, code, QA, maintain, and tools for ops for the entire stack. Because I appreciate the role of an admin or ops, I'm on a very short list of programmers that admins trust. Many times my design decisions affect how the admins will need to support stuff. I typically give them a few options on how I could design stuff, and how that would impact them. I let them make the choice of how it will affect them instead of just being forced upon them.
I have a decade track record at my company for getting stuff done faster, fewer bugs, and handles feature creep. I can tell you exactly what can or cannot be done and what trade offs there are. I've been told I take the longest to get a product out, but the quickest to a final product and virtually no issues. I'm not the only "me" over here. There are a few others, we get shoved together and pretty much given free reign. I have a much longer design phase than most, several times longer, but I spend a lot of time thinking of edge and corner cases and how to design the system to handle them gracefully and in predictable ways. This is why I'm slow to getting something to show for my work. But the end product is completed several time faster.
Because I spend so much time thinking about the many interactions of the systems that work together and the edge and corner cases those interactions create, I rarely have a "bug" submitted. Nearly everything is a feature, designed to work and fail exactly as I thought it to.
When it comes to these kinds of projects, my manager is just there to help me when I request it.
I really hate customer deliverables, too much feature creep. I prefer to write internal tools for performance sensitive systems. I love writing scalable multi-threaded code. Lots of theory, lots of algorithms and data-structures.
Large systems are a lot like multi-threaded programs. Lots of race conditions to think about, possible pathological worst cases to make sure cannot happen, should be well structured, and are a pain to debug if you don't have a clear vision of what your design should be. I remember writing my first mutil-threaded program ever, fresh out of college at my new job. One bug in production, been running for nearly a decade now. I always thought multi-threading was easy and I never understood why people think it's so hard. Debugging race conditions is easy if you make sure certain race conditions can only happen in certain parts of the code and only under certain conditions. If you design your code such that certain states can only occur in certain parts of the code and the transitions happen in well defined ways, if a race condition occurs, it's simple to know where in the code it occurred and many times how to fix it, without even using a debugger.
Other than it is illegal to sell an organ in any situation. Even if the hospital gets a "free" organ because someone died and is labeled an organ donor, it is illegal for the hospital to sell that organ. They can be compensated for the cost of transporting the organ in the case another hospital wants it, but no net profit should be made.
Since Obama care, my coverage has gone up, my premiums have gone down, and the local hospital has reduced its prices. A local representative from the local hospital came to our work to explain coverage and premium changes because we get our insurance through the hospital network. They said since more people in general have insurance, there are fewer people going to the ER and more people scheduling proper doctor visits, which is driving down costs because the hospital is no longer having to eat the costs of poor people unable to pay a $1k ER bill, but can afford a $80 doctor's bill.
LoC is a bad metric to use for most anything except by magnitude. Anyone can write a large project with many lines of code. Like basing a vehicles ability to tow on how large the fuel tank is, then finding out most manufacturers are putting 100gal tanks on compact cars.
And way too many that code with no design. Better off without them. While they make code that technical works, they create more technical debt than useful code, making a net negative value.
Ideals are not ideal. It's like theory vs practice. Ideals assume extremes and extremes are bad. Perfect is the enemy of good because perfect is an impossible ideal.
Given a history book, my personal conclusion is idealist are at best idiots, and at worst genocidal maniacs.
Many implementations of Node.js are asynchronous. Anyone serious about scaling up a server will require asynchronous from top to bottom. I don't know if LOGO is asynchronous, but mixing the two keyboards for searching doesn't result in anything useful.
Everyone knows the importance of software today and you cant just rip off IP
Won't someone think of the lawyers?! Ohh, yes, you. Thanks:-)
Pretty much all software is built on the shoulders of giants, all of the base work is math theory. The only parts of software that I can agree should be covered by IP is trademarks, User Interfaces, or raw source code.
Slashdot Mirror
Quantum dot displays can, but they're a bit further out. Too bad there are colors that have no wave length because they're an artifact of our perception caused by combining real colors. 3 color pixels with N combinations is good enough for now, until we find something better.
Diagonal lines on 1080p still have "steps". The resolution is not high enough until those go away without anti-aliasing.
I don't care about current monitors, I only care that future monitor could take advantage of the higher color depth without a chicken-and-egg issue.
More and more are going online every day. Remote learning is the hot new thing in education.
80% of what you learn in college is via interaction. During freshman orientation, they make it clear that their primary role as an educator is not to teach knowledge. The key to good answers are good questions, teaching you how to ask good questions is their goal. How many online classes teach you how to ask good questions? Very little time was actually spent as lectures.
I have $600/m in medical debt and that's with insurance that covered 90% of the costs, and with below average medical care costs compared to most of the USA. Throw in another $600/m for rent, another few hundred for food, I require a cellphone and internet access for work, 10% of income to 401k, $150/m for health insurance premium, another $100/m for car insurance.
I don't understand how you live on $750/m and talk like it's easy street. I live in a town with $30k being the median household income. It can be done, I've done it, but I was poor enough that debt collectors effectively gave up on me and wouldn't take me to court because I was too poor to waste their time trying to garnish my wages.
When I lived with my parents or a room mate, $750/m was like being a king.
The millions of young people today, who collectively owe over $1 trillion in loans
50% of that $1 tril is owned by 10% of the students, and on average those students make less than a high school drop out. Sounds to me like for profit schools are preying on the stupid.
Time is money. Unless you are saying someone should be able to spend 10+ years on underwater basket weaving for free. I would like to play games all day to, but I know time is not free and someone has to pay for it.
Of course an Art degree does not mean what they learned is entirely useless, but what is the break even point for time spent learning something not directly marketable and value added to society as a whole? A masters in Philosophy sounds like a complete waste of tax payer money, but I could appreciate the argument for a BS in American history adding value because of a more educated populace for better voters.
At this point, if these basic things are still considered good for society, then make them part of high school. Why not just extend high school 4 more years until 22? It's a slippery slope.
I got my degree by first going to community college (dirt cheap) and then doing online classes at the cheapest state university to finish the bachelors.
For the good Universities around here, few credits transfer from Community Colleges to the University system. Few classes are online, especially high end classes, since most classes involve large amounts of team effort, class room discussions, or hands on work. The capstone project has always been a multi-person team effort where 60% of your grade came from your team mates.
There is a reason they have a 100% job placement post-graduation.
1385 psi anything is deadly in close quarters.
I assume that much water creation would be great support for a land assault. Park off shore, supply air support, and much needed fresh water.
I don't actually use it, but I have read about it when researching scaling issues. From what I've read, calls do not have to be async, but it is the general convention for IO to be async.
in the eyes of executives your managers are ultimately responsible for the project's success or failure, regardless of who actually messed up. So they absolutely cannot just sit back and wait for developers to be done with their work and hope for the best.
Not always. Many of my projects are special requests by VPs and directors that are ASAP with no real deadline because it needs to be done yesterday or very important projects that need tight turn-arounds for nearly everything, like bug fixes and new features, live in prod.
When the normal process can take hours, I can take minutes. It's a trade off. They know I am a single point of failure and there is good reason to have a formal process for most things, but some times customers have outrageous demands and too many hands in the pot makes that impossible. So they throw me at the problem and I design, code, QA, maintain, and tools for ops for the entire stack. Because I appreciate the role of an admin or ops, I'm on a very short list of programmers that admins trust. Many times my design decisions affect how the admins will need to support stuff. I typically give them a few options on how I could design stuff, and how that would impact them. I let them make the choice of how it will affect them instead of just being forced upon them.
I have a decade track record at my company for getting stuff done faster, fewer bugs, and handles feature creep. I can tell you exactly what can or cannot be done and what trade offs there are. I've been told I take the longest to get a product out, but the quickest to a final product and virtually no issues. I'm not the only "me" over here. There are a few others, we get shoved together and pretty much given free reign. I have a much longer design phase than most, several times longer, but I spend a lot of time thinking of edge and corner cases and how to design the system to handle them gracefully and in predictable ways. This is why I'm slow to getting something to show for my work. But the end product is completed several time faster.
Because I spend so much time thinking about the many interactions of the systems that work together and the edge and corner cases those interactions create, I rarely have a "bug" submitted. Nearly everything is a feature, designed to work and fail exactly as I thought it to.
When it comes to these kinds of projects, my manager is just there to help me when I request it.
I really hate customer deliverables, too much feature creep. I prefer to write internal tools for performance sensitive systems. I love writing scalable multi-threaded code. Lots of theory, lots of algorithms and data-structures.
Large systems are a lot like multi-threaded programs. Lots of race conditions to think about, possible pathological worst cases to make sure cannot happen, should be well structured, and are a pain to debug if you don't have a clear vision of what your design should be. I remember writing my first mutil-threaded program ever, fresh out of college at my new job. One bug in production, been running for nearly a decade now. I always thought multi-threading was easy and I never understood why people think it's so hard. Debugging race conditions is easy if you make sure certain race conditions can only happen in certain parts of the code and only under certain conditions. If you design your code such that certain states can only occur in certain parts of the code and the transitions happen in well defined ways, if a race condition occurs, it's simple to know where in the code it occurred and many times how to fix it, without even using a debugger.
The way my manager described himself is the company pays him to make us better. We are his first duty.
omg, I forgot about that comic, thanks!
Kidneys CAN be bought. They can also be sold.
Other than it is illegal to sell an organ in any situation. Even if the hospital gets a "free" organ because someone died and is labeled an organ donor, it is illegal for the hospital to sell that organ. They can be compensated for the cost of transporting the organ in the case another hospital wants it, but no net profit should be made.
Since Obama care, my coverage has gone up, my premiums have gone down, and the local hospital has reduced its prices. A local representative from the local hospital came to our work to explain coverage and premium changes because we get our insurance through the hospital network. They said since more people in general have insurance, there are fewer people going to the ER and more people scheduling proper doctor visits, which is driving down costs because the hospital is no longer having to eat the costs of poor people unable to pay a $1k ER bill, but can afford a $80 doctor's bill.
LoC is a bad metric to use for most anything except by magnitude. Anyone can write a large project with many lines of code. Like basing a vehicles ability to tow on how large the fuel tank is, then finding out most manufacturers are putting 100gal tanks on compact cars.
There are NOT enough people that design and code
And way too many that code with no design. Better off without them. While they make code that technical works, they create more technical debt than useful code, making a net negative value.
Ideals are not ideal. It's like theory vs practice. Ideals assume extremes and extremes are bad. Perfect is the enemy of good because perfect is an impossible ideal.
Given a history book, my personal conclusion is idealist are at best idiots, and at worst genocidal maniacs.
He just can't control himself because arguing with you is like arguing with an anti-vaxxer. Free is Free for everyone or free for no one.
Many implementations of Node.js are asynchronous. Anyone serious about scaling up a server will require asynchronous from top to bottom. I don't know if LOGO is asynchronous, but mixing the two keyboards for searching doesn't result in anything useful.
My guess is something triggered a spam filter. Something akin to Occam's razor and Hanlon's razor combined.
ISPs, not services. FCC made a clear distinction between Internet Access Providers and Services on the Internet.
Then Google switches to one of these distros, now what?
Everyone knows the importance of software today and you cant just rip off IP
Won't someone think of the lawyers?! Ohh, yes, you. Thanks :-)
Pretty much all software is built on the shoulders of giants, all of the base work is math theory. The only parts of software that I can agree should be covered by IP is trademarks, User Interfaces, or raw source code.