The app seems like it could evolve into a personal CRM, which is obviously a seemingly promising idea. Really not a fan of the look though (Fisher Price UI design trend).
I have been doing open source for 4-5 months now (main project has 1.8k stars on Github so far), so I am a newbie. However, I have always found ignoring people to be difficult. I immediately get a sense of guilt when doing it.
It is honestly crazy how many times Jobs was able to force his personal choices into the designs of Apple products, and then force the entire industry to follow suite thanks to the influence of Apple. And I am not even mad, he was correct (in hindsight) multiple times - styluses, Flash, and so on. Even in death, he may be proven right about his dislike of fans.
You are in way over your head if you really think junior devs (or others without much experience) are the only ones who can take something away from Dieter Rams' design principles.
Personally I agree, especially when reading long documents, but that is obviously subjective. However, I swear I have met people who always turn on dark modes, regardless of the type of content they are consuming.
Dark mode matters, but so does light mode. I think the option should always be there for your users, since it seems like the population is split pretty evenly in their preference for one over the other. Evangelizing for only one mode is missing the point in my opinion.
On a side note (and not to come off as spammy), but I built a front-end framework specifically to make it easy for web devs to include dark mode (along with light mode) in the tools and dashboards they build: https://www.gethalfmoon.com/
This is truly a blessing. On my last job with normal working hours, I would be sleep deprived for weeks on end. I would literally sleep all day on the weekends. It was the worst, and I could only do it for 4 months.
I pray that this becomes more well known and accepted. For as long as I could remember, I have been uncomfortable (to say the least) with a normal sleeping schedule. School life was literally the worst, having to wake up at 8am. And this stuff has to be genetic. My mother has it, and so does my sister. I have also heard anecdotes from my mother about her father struggling to sleep at night as well.
This is all so confusing, and I am a professional web developer. You may have a great product, but it is literally buried under a mountain of marketing jargon.
This is something I really struggle to understand about the modern web dev mentality. What is exactly so bad about reloading a page? You get visual cues that the browser is doing work, and the page you requested is being downloaded. On the other hand, some SPAs literally provide zero cue when a route has been changed, which is just awful UX to me.
Note that Byju's reported revenue in 2019 was $78M, so we are looking at a multiplier of around 140! Probably nothing shady though, just VCs being VCs, hoping to unload this on the public through an IPO, make their money and get out.
You have a fully working application where the only major issues can be easily fixed by adding `event.preventDefault()` to the keystroke handlers. Instead, you want to throw all that away and rewrite it with some new tool/framework, inevitably introducing new bugs and issues. Unless this is a joke, the question is why?
Fully agree with this. These discussions are always this or the other, but you can easily have both in the same project. Django's ORM and raw SQL functions prove that.
I second this. For example, Django's ORM is actually very advanced these days, allowing you to squeeze out the performance in many, many cases. While I agree that ORMs should not always be used (sometimes you just need raw SQL, especially on very large databases), I think the ORM hate is a bit overstated on HN.
I don't agree with this notion. A website is (and was in 1999) infinitely more useful, immediately creating value for your company/brand. On the other hand, I don't even know what AI means these days.
One tiny advice, all the buttons on your website have anti-aliasing on the text. Anti-aliasing works great on large text, or small text, if it is white in color on dark backgrounds. In your case, the smaller buttons have readability issues, especially the "Signup/Login" button on the top right.
This exact same comment is found in literally every one of these types of threads. And the answer is fairly obvious: audience, and forceful conciseness thanks to the platform constraints. I really wonder when this cycle of typical HN cliches will go away.
>The problem with the "semantic web" projects is that they are always proposing "pie in the sky" projects
I have read this sentiment countless of times, but I don't quite understand it. Maybe because I am not familiar with the semantic web. Can you please suggest some reading list for a person who is unfamiliar with semantic web to better understand these issues?
It is difficult to predict these things. If you are targeting the web (as you mentioned you are a web developer), I would say it's very hard to bet against JavaScript, for good or bad. However, I think the future for Swift devs is bright as long as they are willing to specialize on Apple's family of devices.
This is interesting. Having a structure can help you write better resumes, so this could have some utility. However, as of right now, some of the results contain a lot of gibberish.
As an Asian who has been to the USA, I find this to be highly unlikely, especially considering that Asians (East Asians, not Indians) are not even Caucasians. Whiteshift happened because all those nations (Germans, Irish, etc.) are of Caucasian European stock. Maybe it could work with Hispanics, but even that is a stretch. Many of us don't want to admit this, but our brains are wired to immediately understand how much genetic history we share with another person just by looking at them.
So the majority situation could be easily explained using the positive stereotype of Indian and Asian kids taking their academics very seriously, partly due to the support (and pressure) they get from their families.