you can buy your own health insurance. This is like saying that because you dont get free lunch anymore that losing your job is "life threatening". Somebody has to pay for it. This liberal mindset of "make rich guy pay" is at its core lazy and selfish.
I think that the health industry itself is a scam, and over priced by bureaucracy but that doesnt mean that another person should take your burden. Your health is your responsibility not your employers.
Employers shouldn't be playing health insurance because that shouldn't be necessary. Minimum wage should cover basic care. Either minimum wage is too low or basic care is too high. We kinda take care of this through taxes but its a bandaid on a corrupt overpriced monopoly industry.
In this climate you can't buy your own - its 3X the cost and not subsidized by your employer makes it worse.
But I agree the connection between health insurance and employment is artificial. I'd rather see some basic universal health, plus a market for better plans.
If you get health insurance via your employer, the value of that health insurance is not considered income, and is tax-free. If you pay for it yourself, you get no tax benefits for doing so.
This is not true (at least if you are a contractor or are self employed). You deduct your health insurance premiums (and all sorts of other expenses like home office) as business expenses. After that’s done you pay tax on the rest. source - I’ve been contracting for 6 years and buying my own insurance.
do you work with Laravel ... it has not advanced dev quality of life. It has great marketing and has grabbed a % of the dev base so lots of people work with it. It has done nothing better than symfony, codeigniter, Zendframework.
I feel it breeds bad coding habbits, many coders like it simplicity but when they use it they implement many inefficient functions, mostly around querying the database. Laravel has this robust query builder api so you have many novices accessing the database through it without understanding what they are doing.
I dont really know what "quality of life" is provided by Laravel. Its just another MVC.
Quality of life is better because you can build so much, so quickly with laravel. There is a ton that laravel can bootstrap for you out of the box and then add to that the very large ecosystem of plugins that has come out of the community.
Healthcare has little to do with health. Its this thinking that is the reason why Americans are declining in quality of life.
Stop blaming the other, its not making you stronger or better. Better healthcare will not stop you from drinking too much , eating too much, not exercising enough. No drug is going to fix your social anxiety. Drugs fix symptoms not causes.
This "health disadvantage" what is it exactly. I bet its lung and diabetes issues. We do it to ourselves. Once you accept that you will see the fix. Its not some billionaire giving you money , it you not giving money to the drug dealing (alcohol, unhealthy food, weed/tobacco/vape) billionaires and getting active.
Religion used to be a good way to get out before, a secular nation needs to find a similar motivation that gets people out of their houses. Maybe the worst drug is the media keeping us planted in our chair. Either way I dont trust the gov. so even if we put more money into "healthcare" they would fuck it up. Prove me wrong.
But access to afforable medicine will definitely fix a big chunk of my anxiety about not being able to afford medicine!
"I bet its lung and diabetes issues."
It's really hard to take care of diabetes in america, due to the costs of adequate insulin and related medical purchases such as bloodwork and glucose testing devices.
This is a diversion and a false dilemma. What you're saying is not wrong in that people should live healthy lifestyles, but it is also true that the health care system is now strongly disincentivizing preventative care, early treatment (or any treatment) in a way that can lead to increased mortality.
unless you actually start with these language , then move to loops. Which is really easy. Map/reduce is fundamental to scheme like the closure is fundamental to javascript.
Im not sure how many colleges teach it 1st year but Northeastern University uses scheme as the intro language. The professor there wrote the blue book.
Actually I think you do know of more than zero universities, since you replied to a comment that named Northeastern. A sibling comment to yours named another. Here's another: https://cs.brown.edu/courses/info/csci0170/
Just close your eyes and when you learn about recursion, closures, serialized data, evaluation, ... in Javascript, then just pretend you are using Lisp with a fancy notation. Even the original developer of Javascript wanted to do some Lisp/Scheme, was hired to do so and ended up with a slightly different language...
browsers + javascript + css (frontend opensource) ... to backend , many frameworks for each langauge, many languages all documented ... to persistence layer (mysql , postgres, mssql), and finally server but as OP said thats on amazon, Azure, Dreamhost ... etc
OP is discussing more so the practice of professional dev for 70 - 90% of the devs. Business guys want results , they dont care about scaling and so its about getting it out ASAP. Theres alot of politics, I was taken aback at first, with the idea of CS/software being very technical but it seems that this creates more of a differentiator for political manipulation, cause everyone is already skilled in analytics.
I could go into more detail but basically its all there and a search away (google). In fact there is a term in the industry called "google-fu" (like kung-fu) which means the number of searchers you need to perform to get an answer.
Its a double edge sword. All devs are on their own for learning, but all the info is out there, you just need to be willing to search and learn.
Sadly many people are not like that, and that seperates the good dev from the bad dev (besides the politics).
I assume its the same for being a surgeon, that all you have to do is study and learn the info and you can do it. But having a steady hand is very important. And sadly , if everyone had a steady hand , you'd still have the same amount of surgeons. Those who can do. You want to be a dev, open up the next tab and type into your tool bar "how to learn javascript". Realize that devs created this tool for you, and if you are not a dev its because you dont want to be. Its all there, the web is your oyster.
> browsers + javascript + css (frontend opensource) ... to backend , many frameworks for each langauge, many languages all documented ... to persistence layer (mysql , postgres, mssql), and finally server but as OP said thats on amazon, Azure, Dreamhost ... etc
All of that requires a significant amount of engineering and coding to get working. Just using a frontend framework does not give you a working application, you still have to code that application.
As somebody who develops storage systems, I'll bet that what you consider "back end" is still multiple layers "front" of where I sit.
> server but as OP said thats on amazon
You do realize that Amazon employs thousands of coders to create that platform, right? And "borrows" code written by even more thousands, from firmware and kernels up to databases and similar? I'm sure they're still far outnumbered by the front end glue-writers, but there are still enough to create a culture worth writing about.
I think you are describing the work of a junior software engineer. Sure a junior engineer can do "google-fu" and glue together a working application but there is so much more to being a software engineer than that. Here is just a sample of the kinds of things a more seasoned engineer has to consider when developing an application. Note that none of it can be solved by simply googling and glueing in another open source piece of kit. It requires careful consideration and knowledge/experience that lets you make these decisions.
Frontend:
- Should I use a frontend framework with backend API for a single-page application? or use a standard web site with no distinction between frontend/backend.
- How will I handle mobile responsiveness of the html/css?
- How will I server css & js assets? Use a CDN or host them locally?
- Will I minify css & js?
Backend:
- What business requirements will I take into account when choosing a language/framework?
- Is speed and concurrency a must (perhaps choose Golang)? Or rapid prototyping and complex business logic (perhaps Ruby on Rails or Django)?
- Will I write a monolithic application or go for microservices?
- How important is security? Will my framework prevent vulnerabilities like XSS and SQL injection automatically?
- What web server should I use? What kind of scaling requirements do we have?
- How will we handle version control? What processes need to be put in place around deployment?
- How do we handle deployment?
Database:
- Relation SQL database or NoSQL?
- Are there any cases where I will want to de-normalise my data right away or should I wait
- How can I design my schema to be flexible yet still scalable?
- What columns need to be indexed?
Hosting:
- Use a cloud host? (AWS, Google, Azure...)
- Do we need dockerized deployments?
- Should we use kubernetes or a more managed solution?
- How important is vendor lock-in?
- How do we handle config secrets (like API keys)
- How do we handle changes in configuration (i.e. use Chef/Ansible/Terraform etc.)
>All this advanced tracking/planning stuff from companies like Atlassian seem to me like some kind of weird, dystopian "C-Suite-Porn."
no matter how good the software is , the people using it can make it suck , especially something like communication software
Ive said that things like jira are all about clarity , organization and making process strict. If you dont have that then the tickets become a bunch of unproductive threads.
Also with enough determination you can turn an excel/google spreadsheet into a good bug tracker
I think their software is pretty good , but bad PMs bad process and it doesnt matter. If you managers cant decide a consistent way to run a sprint youll never be able to efficiently record and track it.
Its like we are putting the cart before the horse. Before we can create a good organization tool we need people that want to be organized.
Basically syntactic sugar taken a step further.