For me, I think it has to do with ..just having done more, experienced more.
When I built blanket forts as a child it was something new, my first attempt at building something. It was exiting to figure out how to do it, and enjoy the end product. After a few of those it became a bit more usual, and I started doing other things - play with model cars, build lego sets, etc.
I recently tried welding and I felt that same tinge of excitement - I'm gluing metal together! It's basically magic, I'm taking separate parts and turning them into one. I'm not welding purposefully or to build something, I just really like the act of welding.
Welding was new to me, I never experienced it. I think as a child I everything was new to me, the way welding is. I approached the world with a curiosity that drove me to play with it, to figure it out.
But now I've figured a lot of it out. It's not as fun to play with anymore, because I've exhausted all the angles of play I could come up with (and I did that a long time ago).
I still find that curiosity that drives me to play with something, to figure it out - but I have to look for it, find aspects of life I haven't experienced yet.
The World Cup when you’re 8 or 12 and not really seen one is incredible, at 40 it’s still great but I’ve seen 10 Euros or World Cup’s now and I still enjoy them, just not in the same fascination. Maybe I should try to see them through a new lens.
Same here, I was curious about Kagis low ranking, and couldn't replicate the search results. Also saw ublock Origin on #3, good results for tires, transitors and snow, etc. I've never used any of the Kagi search result weighing features.
Ctrl+F on the page for "System prompt" doesn't show any hits. Given how important those are for ChatGPT (another thought - was the author testing GPT3.5 or 4?) I'm not sure how much weight to put into the ChatGPT results either.
Not sure how much I can take away from this comparison.
I asked GPT-4 about Youtube Downloader and it rambled on about how downloading videos is against Youtube’s TOS and I should buy YouTube premium which has the download feature.
Getting any useful data from GPT-4 about anything even remotely “illegal” is a waste of time.
With a better prompt, you can get it to list some, but it’s very annoying to do so.
Mistral showed that their medium model is far better (yet not good), and the same prompt as in the article gives only one instead of 3 paragraphs of rambling about copyright, and then lists 3 categories of options with examples for each (not good, because ytdl is not one of those listed).
Funnily enough, both mistral and GPT4 apologize profoundly and almost with the same wording when asked "Why did you not mention the very popular, free and open source "youtube-dl" software?" and then mention how/where to get it and how to use it.
> Funnily enough, both mistral and GPT4 apologize profoundly and almost with the same wording when asked "Why did you not mention the very popular, free and open source "youtube-dl" software?"
Likely because they were optimized for general population, which would not have a use for command line python utility.
I’m clear why they didn’t include it, I wanted them to tell me why, though. And I thought that both of them apologized in almost the same way, was funny.
The author already alludes to the fact that you can probably prompt-engineer around this and indeed, as soon as I added a blurb like "these are my own videos that I own the copyright to" it did suggest a bunch of third-party tools and let me ask it about what third-party tools I could use.
It suggested '4K Video Downloader', 'YTD Video Downloader', 'JDownloader' and 'Clipgrab' at first and when I asked for cli tools it came with 'youtube-dl', 'yt-dlp', and 'ffmpeg'
Those seem pretty reasonable results to me but I'll readily admit I don't know (yet) if 'most users' would ask these follow-up questions.
I've experienced both, and I prefer the mono repo.
Our challenges with multiple repos mostly revolved around builds and orchestration. We had to apply all build/deploy changes to all repos, and that increased the chance of doing some small thing wrong. Finding what exactly is wrong with one repo that should be the same as all the others was like one of those "find the differences" pictures. Really annoying.
This is more microservices than multi repo related, but making sure all the different services are released in sync was hard and annoying and often caused issues. Eg a specific API was updated and released but the for a consumer had to be rolled back and the rolled back version wasn't compatible with the new API. So current version and roll back wasnt an option. Rolling back the API would require rolling back all consumers but crap, one of the consumers applied a big migration to our core database and rolling that bank would take forever. And so on.
Just tons of little edge cases that went wrong at the worst time because it was so hard to foresee all the issues.
Monorepo and monolith is so comfy. Want to share code? Move it up one or two directories and import from there. No issues with two bundled react versions in two builds. Easy to refer to code from other teams, never an issue that someone forgot to add you to that one repo almost no one uses but that you need to commit to during firefighting.
I'm not saying multi repos/micro services can't work, but it's hard - you need strong processes that prevent people from being lazy, you need monitoring and management well defined, you need extra tooling that's aware of the repo structure, you need a strong story around migrations, and so much more.
I currently work with a mono repo
monolith that over a thousand devs contribute to daily and it's Cindy comfy. It feels much easier to fix too many devs in one repo (primarily via strong compartmentalization) than to fix too many repos/services
React is a view library that doesn't even provide a way to do XHR requests. Angular is a complete framework. They are very much hammer and screwdriver, completely different and incomparable tools.
There seem to be a lot of people thinking front-end is just a mess of different options all doing the same thing. And the same people show little understanding of the complexities and nuances of front-end solutions.
OK, to be explicit: React ecosystem vs Angular. The difference between to two is how to separate the concerns - inside on large package or into an ecosystem.
I work primarily in Django. I could have given the same comparison of Django vs Flask. The pedant would say flask doesn't have an ORM, and would be correct.
Given the context of this article and HN in general I thought the shorthand referring to React generally would be understood.
Lasso Data Systems http://www.lassocrm.com/ | Senior Front-End Developer | Vancouver, BC, Canada | Full-time | REMOTE or On-site, CANADA only
Lasso is a leading CRM for new home builders and real estate developers. We've been modernizing our app for the last few years, moving from a PHP stack to an Angular.js app and a Java-based REST API.
Now that we're done with most of the legacy-porting work, we've got a lot of new features to build and that's where you would come in.
As a Senior Front-End Developer you would take requirements from the Product Lead, create wire-frames and mock-ups, gather feedback via user interviews and finally implement the features in ES6, RxJS, Bootstrap and Angular.
We offer:
- full-time remote work. Most of our developers are working remotely all over Canada. However, if you prefer working in the office you're welcome to go there. It's located in Richmond, BC.
- when you start, we'll provide you with any hardware of your choosing
- a tools budget of up to $300 per transaction you can use to buy whatever you need to stay productive - no authorization needed
- formal education matching (up to $1500 yearly) and funding for other continued-learning courses, conferences, and workshops
- competitive Vancouver salary
Lasso has a very trusting and open work-environment, without fixed work-hours, imposed dead-lines, or in-office requirements. That does require you to have good time management skills, and be comfortable with self-directed work.
If you're interested or want to know more details, please message me at thomas@lassocrm.com (include your resume if you're applying :) ). I'm the front-end lead and have been happily working here for four years.
I am considering transitioning from my current position as a senior front-end dev to a different environment. Pretty comfortable and already working remote full-time in Canada, just looking for a change and maybe a bit better compensation.
Pretty sure I tick all your boxes in the requirements section and already experienced working remotely. Any chance you can disclose a salary range you are aiming at?
I'm happy to answer any questions you have, salary too, if you send me an email. Sadly I can't publicly disclose our salary range, so if you're willing to bear with me and jump through the emailing-hoop I'd appreciate it.
This happened to me. I worked on a side project in high school that grew into a company after about eight years of work. Three years and a pivot later we gave up due to decreasing traction, and returned whatever funds were left to the investors.
I moved back to my parents for about a year to work on other side projects, but ended up looking for a job and found an awesome small company that I'm very happy working for. I'm still working on market-focused side projects and without the stress of having to make money/gain traction it's a lot more fun. I really prefer this setup, especially since a small company allows me to scratch most product-development itches I have since there's not a lot of bureaucracy.
A lesson I've learned: Quit early. If you feel bad about the project right now, end it as soon as possible As in, tomrrow. Don't stick around waiting for the big break. I've done exactly that, and while we actually ended up with some paying customers after our pivot, we would've had to achieve an insane growth to be worth anything to my co-founder and me due to the dilution of our shares. It's not worth basically building a new company for the smaller fraction of shares you have after taking an investment.
She's not saying "this is going to be a professional design for your next project", the title itself contains "half-decent".
She's providing insightful tips for developers to make their pet projects look..like they're not designed by engineers (we do tend to make a mess of things).
And the advice she gives is perfectly fine for exactly that. There are fonts that look good together, subtly textured backgrounds do look better than simple, flat colored one's and using basic color theory upgrades a websites look (teal vs. orange, cough). Together, they make something that looks half-decent.
When I built blanket forts as a child it was something new, my first attempt at building something. It was exiting to figure out how to do it, and enjoy the end product. After a few of those it became a bit more usual, and I started doing other things - play with model cars, build lego sets, etc.
I recently tried welding and I felt that same tinge of excitement - I'm gluing metal together! It's basically magic, I'm taking separate parts and turning them into one. I'm not welding purposefully or to build something, I just really like the act of welding.
Welding was new to me, I never experienced it. I think as a child I everything was new to me, the way welding is. I approached the world with a curiosity that drove me to play with it, to figure it out.
But now I've figured a lot of it out. It's not as fun to play with anymore, because I've exhausted all the angles of play I could come up with (and I did that a long time ago).
I still find that curiosity that drives me to play with something, to figure it out - but I have to look for it, find aspects of life I haven't experienced yet.
reply