2,431 karma · joined March 21, 2012
Articles like this one might encourage me to give it another go. Is there a distribution that's considered the 'best' for a KDE environment or will any do?
I also love that Singapore is both 'developing' on this list and int the Small Island Developing States list, despite it easily being in the top 10 of most developed countries in the world.
JS has lost against TS which is basically C# for web (both designed by the same person) and Python is not really something you should build large applications with (execution speed + maintenance issues).
What do you believe is the current language du jour?
* The above is just applying an existing (useful) feature to a different context. So there isn't really much learning needed, it now just 'works as expected' for assignments and I'd expect most C# engineers to start using this from the get go.
* As a C# and C++ developer, I am always excited to hear about new things coming in C++ that purportedly fix some old pain points. But in the last decade I'd say the vast majority of those have been implemented in awful ways that actually make the problem worse (e.g. modules, filesystem, ...). C#'s new features always seem pretty sound to me on the other hand.
For me the reverse thought always comes into mind: "The amount of tangible work achieved when in the office is close to zero". Countless chats, interruptions, distractions, meetings you can't easily get out of, getting in late due to traffic, having to leave early due to childcare, etc. Even if a person spends half a day WFH not doing any work, it will still be more productive than being in the office.
When I say work, I mean actually producing tangible assets.
Brainstorming, design, anything that requires high collaboration, works much better in the office when everyone is in attendance.
The end result of this is that the most productive environment for software engineers is a mostly WFH schedule with anchor days in the office to hash out the collaborative tasks in big blocks. This translates into 1-2 days in the office depending on the team and the current phase of the development lifecycle they are in.
If you have a person in your team who consistently does not perform any work when working from home, then that is a performance management issue that should be dealt with like every other performance management issue. I do not really see why 'wfh' makes this special.
So far I have seen Google Maps be pretty useless in parts of Asia with their own software infrastructure (e.g. Korea or Japan) but it's been very useful in most Western countries.
I'd immediately look into what happens for odd numbers, rounding, implicit type conversions etc. Or at least that's what I was taught when I first started programming.
Also relying on "well we know that X is always Y" is almost always a mistake; maybe not always at first but definitely in the future because X will almost certainly be Y at some point. Defensive coding would catch such issues (with at the very least an Assert somewhere to ensure X is indeed Y before continuing, ensuring that we get a nice error when that assumption proves to be wrong).
No idea how they justify the time and cost over there.
Then again they pay tens of thousands of dollars to install solar when it's 1/10th of the price here.
I've noticed this as well; especially with the more abstract professions that have words like consultant or strategy in them. Even from friends you'll often get a surprisingly 'corporate-BS' answer.
The best answers I've gotten is by asking people to take me through their last work day hour by hour.
Then again, I've had plenty of people not understand my job either: "I build software applications" sounds obvious to us but I've had people ask the follow up "So how do you actually do that?". The answer they're expecting is something like "I sit in front of a computer and type text into something equivalent to notepad".
* Controlling items I don't have easy access to:
* AC in baby's room (as well as checking on temperature) while baby is asleep
* Subfloor ventilation fans and set up clever timers for them (I'd have to crawl under the house)
I also have a motion sensor connected to a light for the hallway which has logic that is a bit more clever than the out of the box motion-controlled-lights (e.g. it stays on if people are in the vicinity).Other than that, the rest is pretty much gimmick: Every blue moon I will change the light in the living room to bright purple for fun.
Is that true? I was surprised when looking at the actual stats (most people in Sydney drive to work), but maybe there are many more people working in places other than the CBD skewing this.
When I was cycling in from Balmain, there were a huge number of cars stuck in traffic getting into the CBD every morning. Despite it only being an easy 15 minute cycle (or a 15 minute bus ride) from the peninsula.
I vaguely remember hearing about it but never tried it out. Not sure when it was canned. The software part sounds very interesting but could also be sold to existing transit companies and government agencies to improve their network.
I've had it fail similarly where it saw some text, messed up the OCR and was then lead to a wrong conclusion.
It was pretty simple and worked well, especially compared to having to give bank account details.
That being said, I am in Australia now which has a similar system and I'd say 95% of my friends just give me the bank details instead of saying 'just use PayId with my phone number'.
However, the coding assignment was a really good filter and allowed us to dismiss the majority of candidates before committing to a labour-intensive face to face.
I haven't interviewed anyone since AI took off, but I am assuming that from now on the majority of candidates that would usually send us crap code will send us AI code instead; thereby wasting our time when they finally appear for the face to face.
Have you encountered that yet?
It's used between private people to make it easier to send money to one another without having to type in bank account details, but never really used to pay businesses (except under the table).
How come this is so popular in Brasil for paying businesses vs using a card or your phone to tap and pay (which seems more convenient)?
But that's also true in North America.
Last I checked, Air Canada was not advertising themselves as low cost.
(Btw, transcontinental is an American term that confusingly means from one side of the US to the other, and not 'between two continents')
Air France, Lufthansa and BA all have carry-on included in the fare.
If by "any European airline" you specifically mean Ryanair, then yes. We can expect people to pay if they did not print their boarding pass themselves.
It's actually surprising how many articles on 'respected' news websites have typos. You'd think there would be automated spellcheckers and at least one 'peer review' (probably too much to ask an actual editor to review the article these days...).
But I think there's a difference between someone who 'teaches' you and someone who is at a high enough level to discuss ideas or issues with you.
For example, in my first job I 'learned' the most not from the senior engineers around me but from another new grad who was just as curious as me. We would discuss issues we're having, brainstorm solutions etc. It was not so much that I learned from him, but that I had another brain of similar competence that I could fling ideas at.
Not having such a person makes your job more difficult (as you might find yourself in a rabbit hole and desperately need someone else's perspective) and much less enjoyable.
Imagine not having a competent dev in your team to review your code.
I think the only other country where I regularly got jolted up (nearly hitting my head on the ceiling of the car) was India.
I have the same anecdotal experience with a possible explanation:
Inexperienced engineers often don't see the greater picture or the kind of edge cases that will probably need to be handled ahead of time. I've often had the following type of conversation:
Engineer: "I think that would be a day's work"
Me: "This will need to interact with team X's package. Have you accounted for time spent interacting with them?"
Engineer: "Oh no, I guess two days then"
Me: "Will this account for edge case 1 and 2?"
Engineer: "Ah yes, I guess it would be three days then"
Me: "Testing?"
Engineer: "Maybe let's say a week?"
On the other hand experienced devs might have their judgement clouded by past events:
"Last time we did something with X it blew out by 3 months" - Ignoring the fact that X is now a solved issue
Another good one is for the phone to stay on hold for you. That one has been extremely valuable to me as Qantas would regularly keep me on hold for over 5 hours when I tried to get my money back for a cancelled flight. The operator would sometimes be a bit confused when I pick up, but it usually worked well and certainly beats listening to hold music for hours.
The amount of times that I have had to go to the numerous different kitchen areas only to find out the employee left the building to get coffee or run an errand is just as high if not higher than someone being 'away' on Teams when I need them. Only at home I just set an alert for when they're back online instead of attempting a wild goose chase.
I don't need to forward any ports but seemingly because I share an IP with a billion people I get Captchas everywhere (Google, Cloudflare etc.). I was even blocked from accessing Reddit without an account at some point.
ReadOnlySpan is so powerful because it can be used generically and has implicit conversions that allow you to improve the speed of existing methods without breaking backwards compatibility.
It's well designed and that takes thought and time.
Could you expand on that? I load all my books via calibre but I also have the kindle set to aeroplane mode at all times. Does this happen when syncing?
> The US is a different world than most countries which tend to be geographically tight and culturally homogenous
I am not sure how much you know about Australia, but homogeneity and geographically tight is definitely not how you would describe it.