Then you accidentally delete the open bracket and the predictive naming gives options for similarly named functions or objects, so you hit delete again (because you haven't really internalized how to avoid every type of autofill on every app that's shoving it down your throat), the suggestion list grows, so you hit space, thinking that you just need a little fucking space to think, which fills the autotext, so you hit space again because at least there will be a fucking space to suppress the suggestion list, you hit the left arrow key to hop over your Demilitarized Zone Space, delete the erroneous element and start typing, but that plugin you installed last week autotrims trailing spaces (what a time saver!), so once you finally get the function/object name you look away and hit the right arrow to hop over that DMZ Space, but that space isn't there, so your cursor goes to the next line and you start to type, and when you look back to see this, you start hitting delete until the cursor gets back to the line above, but you hit delete one too many times and delete the open bracket, so the predictive naming shows up...
Pretty sure LibreOffice has had Python capability for quite some time and which doesn't run in the cloud.
Willing to bet that the dialects are sufficiently different as to be not cross compatible though, and Microsoft will no doubt have some kind of marketing / FUD about why theirs is superior. Unless you're working offline, I suppose. "But why would you ever want to do that?!??!!??!"
I feel this way about open source and the seemingly frequent lack of detailed code reviews. This one project had two function options to use from a library. One handles errors by returning them to the caller so they can be handled gracefully. The other, calls PANIC! They chose the latter and it causes a crash loop for a relatively easy to hit code condition that is sensitive to User input.
Why ask for unit test, in the code review, when you can just accept the contribution for a feature that is used in large corps.
I will say I hate having to pester folks to do review on a merge. The place im currently at requires two and its pulling teeth to get folks to look at someone elses code. well except for me I always treat merges as priority as that is ready to go whereas with mine if I have not merged then its not that ready.
We actually started as a PHP developer, and our last PHP job we worked for a unicorn: A well architected, well commented, well written, modern PHP codebase. Never seen anything like it before or since.
Just wait until you get a T_PAAMAYIM_NEKUDOTAYIM error!
Programmer Humor
Hot