We've figured that out, but certain members of society decided that extracting wealth through protectionist zoning/building code behavior is much, much more lucrative.
that just moves the figuring out one step to the right. knowing how something will work but not knowing how to get it implemented means the problem is not completely figured out yet.
Exactly. We haven't figured out how to solve the problem, because we still have the problem. Maybe it's unsolvable, and it's just a limitation in our ability to live together in large numbers. Or maybe we need to redirect our spending on (among other things) frightfully expensive experimental medicine and spend the money on things that are a lot cheaper and will help a lot more people.
Really? I think I can agree that the zoning isn't helping, but claiming we have figured it out seems like bold claim. Where _is_ it working? My impression is that housing costs are increasing faster than inflation and wages not only in North America, but also in the UK and EU, which don't have the same kinds of zoning laws.
Aren't Japanese homes super tiny? Even smaller than the already small homes and apartments in Europe? That's one reason. In the US, it seems that people live in bigger places, with higher ceilings.
My understanding was that Japanese housing costs are only good in USD because the yen is devalued. I had the impression that housing is expensive relative to local wages. Is that not true?
It's not true. Here is an apples-to-apples comparison of the price of residential property between the US and Japan in real (inflation adjusted) terms.
In my experience, formatting is just about the only thing that a department/university cares about (outside of the folks on the committee), and they will send back a thesis until they're satisfied with the formatting, and that means lost time. Perhaps throwaway_7274's department has a reputation for particular attention to (meaningless) detail.
The matter isn't really that something is possible only in latex, but that a department/university might have its own template/document class of arbitrary complexity that you would have to reimplement
> department/university might have its own template/document class of arbitrary complexity
I think there is a limit to how complex they can be. If you can't do it relatively easily in Word, then it's probably going to create too many complaints for the bureaucrats
I think there’s a Latex template you can use, or you have to make your own document that looks as similar as possible. It’s not a list of guidelines but a template that specifies how it’s supposed to look.
that is a good observation, but it actually proves that the riskiest thing you could do with your time is a meaningless credentialist PHD, instead of actually learning skills that rich people will pay you for immediately without the pomp and circumstance
If you don’t understand what they mean and are hunting for pedantic discoveries in explanations of a problem, then please try to dig deeper and contribute more meaningfully, as per the HN guidelines.
> to use a different program for turning equations to pixels?
They explain in the comment why it was risky (new thing instead of tried and true methods, not a large user base, etc.) and yet you minimized their explanation, over simplified and seem to not understand the risk involved in writing one of the most important pieces of literature in one’s career.
> why? they wont give you a phd if a single pixel is off by one bit in the alpha channel?
They meant pixel perfect as in matching the template to infer the importance of this. Then for some reason you went down the “off by one bit in the alpha channel” which is a bit of wise-assery and not meaningful nor necessary to the conversation.
As I said before, please dig deeper and use your well meaning System 2 to contribute, and not your Reddit-Tainted System 1.
The behavior wouldn't exist if the system didn't so heavily incentivize it. How many pizza place owners do you know with a net worth of $10,000,000 or higher, vs how many pizza place owners have ever tried?
Freelancers mostly work intermediated assignments rather than direct assignments. These intermediators have put up what are essentially job boards. If you are well connected, you can get direct assignments via your contacts, or by reaching out like traditional sales work. If there are some avenues to get leads for direct assignments, I would be really interested to find out!
In the USA, if some big and usually "non tech" company like McDonalds or T-Mobile wants to staff a whole project with programmers, they will usually have a relationship with someone like Infosys, Tata, Slalom, perhaps even Hitachi or Tech Mahindra or Accenture/Deloitte. These companies all pay you like a regular employee so you don't need your own drafted employment contract or business entity.
If you howver have a github/youtube channel/website where you make and release your own software, and someone contacts you saying "hello we want to pay you to add more features and or fix some problem for us", then you will need a contract and usually a business entity unless you don't mind being personally sued into the ground.
Such reachouts are very very rare unless your software has gone viral in the right circles, but I personally know at least 20 people who make a full time living this way. It seems pretty unenviable, and corporations whose email domain you would recognize routinely pull support or play egregious games with the definition of done. No cure for life, I guess :)
Large consultancies like Tata also operate in Finland + we also have a bunch of our own consultancies that operate in this manner (their consultants are regular employees of the consultancy). Earlier when I mentioned job boards for freelancers, it is particularly these large consultancies that subcontract down to freelancers via job boards (they try to fill positions from their bench, and when they are unable, they subcontract to other consultancies or freelancers).
Nice! In the US that still happens a fair amount too but I think as the industry has developed it has become much more rare than before. Athe keyword would be "corp to corp" employment, where you as the programmer either have an LLC, s-corp, or c-corp.
But with the amount of accountant overhead and government fees you have to pay per year (including to shut down your entity when you are done), it becomes a bit pointless and there aren't really magical tax savings to achieve that I know of unless you are like, really good at deducting things and surviving IRS audits. In any case, it is rare for corporations to even offer it, but maybe in some super niche areas I'm not aware of, there could be good advantages.
Still I think the hardest part is making and maintaining quality connections with people who value your skills :)
> Such reachouts are very very rare unless your software has gone viral in the right circles
Another anecdote. I had job offers coming out of my ears while I was posting videos of my indiegame on twitter. Only one video had substantial reach -- near the end of my time actively twittering. I think what helps is doing something as well as you can, and be persistently visible.
OpenGL is not so bad because the API is quite stable. WebGL in particular is great because there's literally zero setup you need to do for executing it.
Integrating with Linux/Windows display surfaces is disgusting however. KMSDRM is way, way better than the nightmare that is X11 and Wayland.
You never need to use everything a language provides. You find the parts useful to you or your team and use all of them.
I was a C++ developer for a decade and knew a fair amount of the C++13 spec but never needed to use even half of it in production. I've been a Java developer for years and don't know 10% of the standard library there. That doesn't make either language poorly designed by itself.
Lmfaooooo..... to everyone else reading, cpp programs are indeed successful, but they are successful in spite of cpp, not because of it, is my assertion. It is increasingly rare to find major applications using the newest cpp features, because of how obtuse they are for 99.9999% of people, including extremely good programmers, of which a Youtube search could produce 12
Entirely 100% true. I can count on one hand the times I've said "wow, this documentation was written by someone who cared". Threejs is a good example here, but even then it is subject to API rot and needless reference chasing.
Examples are often the best way to do documentation, sadly.
I've been leaning on test suites more and more for this. It's almost like a test suite should contain comprehensive tutorials. You know the API is good (hopefully) because if it isn't, the CI/CD pipeline wouldn't have let the release through.
