I've been finding myself increasingly annoyed by non-coding managers thinking AI is going to bring 190% reduction of cost, or will replace entire divisions of coders. It's a helpful tool, sometimes, but sometimes also a complete and utter tool. So I wrote this rant about it.
I've used it for 15 years and ST is still the first thing I install on a new PC.
All thoughts, meeting notes, journals, blog post drafts... everything is jotted down in ST first. I even went as far as writing my own to-do list syntax highlighter[1] which is the main reason ST is always open, at home and at work, even though I mostly use VSCode and IntelliJ for coding nowadays.
I also use sublime for managing todo and IDE for coding as my work repo uses custom tooling for build and autocomplete which only supports Visual Studio.
I use PlainTasks [0] which is very similar to your plugin but also has a few keyboard shortcuts to toggle the item state.
Using this with a watered down GTD setup has really brought a lot of peace in both my personal and professional life.
Love the simplicity of your to to-do list syntax highlighter in comparison to todo.txt. That's more how my brain works, as simple as possible. Especially your take on the due date vs. date when you plan to do it.
Will definitely try it out.
Exactly. A video on YouTube posted '1 month ago' is not the latest episode I'm looking for. Much quicker to interpret than a timestamp. Sometimes a fuzzy date is enough.
Especially being from Europe: it is never clear if 10/04/23 means October 4th or April 11th unless you know which date format is being used.
Agree. I also like the relative dates. E.g. on Github where it’s useful to get an intuition very fast of when files in folders/projects were last updated. I don‘t care about the actual dates in this moment, the fuzziness of the relative date is the approximation I‘m looking for.
The apps do, but the website does not. music.google.com used to have native support, but to cast music.youtube.com you have to cast the tab, which is far less than perfect. (Instead of streaming directly from the CDN to the chromecast, casting a tab will stream from your desktop to the chromecast. It works so poorly that sometimes even the pitch changes slightly, like an old timey recording.)
I agree with this comment completely. Adding a biometric lock would turn it into 3FA.
Not sure if HN allows to plug your own apps, so please forgive: I made an app a while ago that aims to replace Google Authenticator for some of the reasons mentioned: it allows to back-up and transfer tokens without creating a large attack factor. Not having sync is a feature in this case as well. In fact, the app does not even have the internet permission enabled, so it utterly unable to phone home. Transferring backups does require a biometric lock.
Biometric data should be considered identity and not authentication data. They can never be revoked or rotated for one. And who knows how many people have it on file. Not every auth server gets their own « key »
Makes sense. The principle of 2FA is to combine 'something you know' (a password) with 'something you own' (your phone). I guess the biometric lock is 'something you are' on top of that.
Not necessarily dark though... as an app developer I'd actually really want to hear the feedback from the people who dislike my app. As in any business, oftentimes the most disgruntled customer is the one that can provide the most useful feedback.
An even smarter way (in my opinion) of getting 5 star reviews is by showing the dialog only after x hours of use. Users most likely to rate badly will have the app uninstalled before the dialog shows.
Which benefits everyone if the problem is a simple thing you can resolve by helping them directly. Support is also part of the experience, and good customer support should factor into the review as well.
I can see how you'd see this as providing a positive bias, but I see it more like getting a chance to see if you can't help the customer out before they give up on your app. It also reminds the customer that there are people on the other end - so even if the issue can't be resolved, and you still get a one-star rating, the level of vitriol seems likely to be reduced - something all too easy to forget when angry-reviewing.
Of course if they just take the feedback and dump it, that's a different story - but again, I would think anyone with that experience would still leave the negative review.
TL;DR - too many downloaders use negative reviews as a combination support request and cudgel. I think this is a reasonable defense against that.
Users with negative experience are more inclined to leave a rating than users with a positive experience, which makes the ratings not reflecting the reality of the overall user experience in the first place. (http://cdn2.hubspot.net/hubfs/232559/The_Mobile_Marketers_Gu...)
This technique is a genuine way to encourage sharing positive experiences about the app. In the same time, it offers a chance to the app provider to improve a bad user experience.
Whether it's a dark pattern or not, I think really depends on the motives, are you genuinely trying to make the app better or are you only interested in the people's perception of it.
I've used Xamarin for several projects and I greatly regret that decision. Granted, most of my hatred is targeted towards Xamarin Studio and Xamarin.Forms so if you use Visual Studio and build only native UIs then maybe your experience will be better.
However, in my experience, both Xamarin Studio and the build system are buggy as hell. Random or inexplicable build errors, things that break during updates, incompatibilities with official Android support libraries... I find myself doing 'clean project and rebuild' to fix random errors, or switching between alpha, beta and 'stable' channels all the time depending on which one does not have the bugs that I'm running in to.
Xamarin.Forms is simply a disaster. Because it aims to unify the apis for the UIs for various platforms it boils down to only the most common denominator of those platforms. And then makes it worse. Not only is it buggy, it is also very slow and incredibly limited. In our office we're keeping a list of all of Xamarin's silliness we encounter, here is just one of those:
"Clicking a Button changes its text alignment from center to left-aligned; it requires writing a custom Renderer to solve this."
I admit that Microsoft is usually quick to fix those bugs, but it doesn't instill much trust in the system if you're constantly running into issues. Many days I am literally working 50% of the time on my app and 50% working/fighting my way around Xamarins issues.
I'd love to hear from someone using Visual Studio if their experience is more positive, but my advise is: please stay away from Xamarin.Forms and Xamarin Studio as much as possible.
I have used both "native" Xamarin and Forms to build apps. Last year Xamarin had a really bad streak with stability but things have certainly improved.
Android itself has so much quirks in development in itself that it is sometimes impossible to abstract away. Xamarin just doesn't show this always so you're chasing the wrong ghost from time to time. Android development is simply madness.
I'm not gonna say Forms is perfect, far from it but it serves a purpose. With a little bit of work I could get everything going that needs to be done. As a single dev I can cover both platforms. If you have the resources go native Xamarin.
Xamarin Studio is actually not that bad, only it has become a bit of resource hog last weeks releases and needs the occosional restart. With the power of MS behind that should certainly be improved.
Xamarin.Forms is now open source, but I really hate that the PR's are slow to being reviewed and 1 contributer is outpacing the Xamarin team in his spare time. Clearly something is brewing, they must be working on something new. Or else they should ditch and start something else.
Forms is not Xamarin. It's a DSL in the form of a NuGet (aka npm/cpan) package developers can use to attempt to ignore the differences between the platforms.
It's kinda like swing. Great for throwing together a line of business application and getting xplat ui for free. It's possible to build a performant application with the framework but it abstracts subtle things that come back to hurt you. For example. Forms apps on Android is a single activity, always, period. Fragments are cycled in and out of this activity as navigation occurs. This introduces subtle annoyances related to memory usage as the entire app must be running vs thin slice. It transforms the lifecycle of Android into the UWP or iOS lifecycle.
Again this is Xamarin Forms. It is not Xamarin. It has its place but please don't confuse the product due to poor branding.
Hi, and thank you for Wallabag! I've been happily using the self-hosted version for quite a while now. At some point I forked[1] the Android app but development stalled when I needed an API to be able to improve the app further. So this v2 is great news!
Just an FYI: in the blog post you mention that the login for the preview of v2 is wallabag/wallabag, however I get 'bad credentials' when trying that.
This new Material Design version looks awesome! Eagerly looking forward to v2 becoming stable so I can upgrade.
I've been finding myself increasingly annoyed by non-coding managers thinking AI is going to bring 190% reduction of cost, or will replace entire divisions of coders. It's a helpful tool, sometimes, but sometimes also a complete and utter tool. So I wrote this rant about it.