Secondly, pretty much any reputable ETF (or combination of ETF's) can quite easily achieve this over 30 years.
1,134 karma · joined August 21, 2019
Secondly, pretty much any reputable ETF (or combination of ETF's) can quite easily achieve this over 30 years.
If it's some kind of encoded message containing information that can be decoded and verified by scientific communicators, perhaps not.
I absolutely loved working from my bedroom for years. It was great (despite the common down falls like the ones listed here). My family used to make fun of me at parties and seasonal celebration "OH YOU'RE NOT IN YOUR PAJAMAS TODAY", but joke was on them after a couple of years - I was making 5 to 10 times what they were per year, and I was waking up at 8:50am with no commute.
I eventually ended up investing in building my own "detached" office in the back yard - a dedicated space set up for working. This was by far the best thing I ever did. It created a visible boundary between home and work life, and I still didn't have to commute or work in any clothes other than my pajamas the majority of the time.
I couldn't image going back to a bedroom now. But even more so, I can't imagine how painful it is for people to sit in traffic every day, stressing they might be late, burning money on fuel and their car, and waking up earlier than they really should.
It's pretty reasonable to think you might spend $100 a week on a commute straight out of your own pocket. That money is gone forever. Now consider if you invest that money over 30 years in some low to medium risk areas and average 10 - 15% per year. That's a healthy addition to your retirement fund of around $1,500,000, plus a good amount of extra sleep.
EDIT: Okay 15% is maybe a bit hopeful and lucky. But still 7 - 10% will make a difference in your retirement.
KDE honestly seems the best for this, although on the latest version of GNOME has fractional scaling available behind a flag (although also buggy and very slow).
Funny thing was, I already knew how to program (in terms of breaking problems down and using components to model data - probably from building games in RPG Maker), I just had never been shown a programming language. It was a "AHA!" moment.
This reminds me of being a kid, and always having the "hacker" mentality. Use whatever you have available to make something awesome.
I remember having my first "computer" based project around 2001 for school. We had to create some kind of presentation "using any tool" available to us on our home computer (or available in the school library).
I opted to create my presentation using RPG Maker 2000. It had animations, sound effects, and even a little quiz at the end. I handed the project in to the teacher on a 1.44MB floppy* drive containing only the compiled windows binary.
The teacher loved it and placed me in a regional school advanced IT program where I was first introduced to QBASIC.
T|null
In PHP 7, you can still do function foo(string $bar = null): void
Which is a little clunky...Surely C/C++ will be the better performer on such a tiny board... And usually you want to squeeze every drop of performance out of tiny boards
The only thing they have added is confusion and behavorial conditioning. I see no benefits of the "new" way.
In my opinion this is still a gentle push to encourage users to just type in a search query instead.
I guess they really want to funnel everyone through search...
A strange side-effect I noticed over this period was being able to find things _much quicker_ than my colleagues. I thought maybe I was just better at picking what words to type in - but after we did some comparisons, DDG really does just provide better results now (and increasingly so) for the kinds of searches we're doing.
The bangs are useful, but honestly I haven't really needed to use them. Occasionally I'll use a !g or !yt, but this is maybe 1% or less of my searches.
I've even taken the rare step of disabling uBlock and some other Firefox extensions because I _want_ DDG to succeed.
Correct me if I am wrong but the only reason non-tech people use Firefox on Android is to block ads.
Perhaps this is a push from Mozilla to try and get some search revenue flowing again?
Even if you don't plan on using it, make yourself aware of the sheer number of requests being sent _constantly_ from not only your applications, but by Android system services themselves.
I'm not saying these requests are always related to ad tracking, but you can't argue there's a lot of information constantly being sent back an forth.
Pro-tip: Your battery life will possibly double running a software firewall on Android...
Is there a difference in their work output? Absolutely there is, in my experience here. Contrary to my prior assumptions, it is actually the _die hard_ tech guys that
- Produce excellent work
- Produce a consistent amount of work over long periods
- Keep up to date with tech
- Don't really seem to suffer "burnout"
- Consistently improve their skills and progress their careers
- Have a high probability of being enthusiastic about a new project, technology or their work
Where as the ones who are "work-only" programmers (not always) tend to
- Produce excellent work in short bursts, and then average work the rest of the time
- Do not produce consistent amounts of work over long periods
- Not only struggle to keep up with tech, but actively _fight_ the idea of having to learn something new
- Have a high probability of going to management to discuss their "burnout" and take extra time off
- Seem to have one specialized skill set that neither improves nor gets worse - they just float around the same level
- Rarely show enthusiasm for a new project, technology of their work
People often refer to "burnout" in the context as a short term solution - but I honestly think that "burnout" as we know it is a result of someone who has already "checked out" or "lost the passion" for what they do (or perhaps, they never had it, and just went into this career for other reasons)
This seems really grim for the non _die hard_ people, so here's some positive traits I've seen in them that are usually lacking in the _die hard_ people.
- Typically have much better communication skills
- Usually better at reasoning for which technology to use in a project (ignore "language or framework of the week")
- Are better with customers and maintaining relations
- Provide more support to their colleagues
- Willingness to take on different kinds of tasks (no attitude of "that's not my job")
I think it's fair to say that balance is key between these very dynamic cultural traits we observe as programmers.
EDIT: formatting
For example, #include </etc/passwd>
All the best
It's still there. It's just a compile-time "race checker", not runtime.
Typically mutex / spinlock is implemented to reduce and prevent race conditions
- It's multi-process architecture redesign _really_ improved performance (it's like using a whole new browser, honestly. If you haven't at least tried it, it's worth a shot).
- Mozilla's commitment to privacy (I know in the eyes of some, their current commitment isn't enough) is the best option you have outside of Safari / macOS.
- In version 71, battery drain on macOS is indeed largely improved
- The multi-account containers, anti-tracking and anti-fingerprinting are a breath of fresh air (yes, I know they are not perfect). I am satisfied that each time I sign on to YouTube, my recommended videos are just a bunch of random things.
- Firefox looks like it will remain one of the only browsers that fully supports current ad-blocking technology. (Yes, I know about Brave, but that's besides the point).
- The devtools section has seen a lot of attention that easily brings the experience on par with Chrome (in my experience).
- Firefox on Android with AdBlock drastically speeds up browsing the internet on mobile devices.
But, despite all of these good points, the browser still feels... clunky.
Sure, the UI performance drastically improved since Quantum, but really, open a fresh Firefox window, browse to your favorite site and click around a little. Then, try the same thing with Chrome / Chromium / Edge. I don't know exactly what it is, but these other browsers just feel that little bit "smoother" or more "modern".
Say what you will about Google and Chrome. But morals aside, in my opinion, there's no denying they built a world-leading software product that has vastly increased the perceived quality expectations of browser users.
Note: I still remain a primary Firefox user. The eye-candy is nice, but for me it's not worth sacrificing all of the other pros of Firefox.
EDIT: grammar
1. It prevents my "flow" from being sidetracked by micro-optimizations that are probably too early to consider necessary anyway.
2. It helps me to retain my short term memory on the code I am working on. If I branched out at each TODO to implement some improvement or method, my brain typically needs to context switch to focus on the fine details of the subject. By the time this is done, and I switch back, I have forgotten key aspects of what I was working on and it slows me down again (i.e. local names, structs, etc.)
3. It allows me to re-approach something with a completely different mind set (given that I come back to it after a signicant amount of times). Half the time I realise that what I wrote was indeed "good enough" and no further time should be committed to it unless a reason exists to do so.
4. It gives opportunity for other developers to see, think, comment and contribute on the subject. I find that typically if I TODO an area, it's good for a second set of eye balls to see it. There's far smarter people than me around, and there's a good chance one of them will find it and propose a better solution.
5. On the rare "quiet" day, I can grep for TODO and just work through them.
Obviously these points are only valid if the TODO labels are being added in situations that will benefit from the above.
Less likely, but not guaranteed. Rust is still very new, which means if people are migrating from writing firmware in C to Rust, chances are they are going to bring across C habbits, which will frankly lead to writing C in unsafe Rust.
The security of Rust is only as strong as the author who wrote it. We currently don't have anyone who started their firmware career on Rust.
I do have to ask though, does this serve any improvement over or fix any of the shortcomings of systemd aside from being written in Rust?