Also, writing a solver for these things is also surprisingly difficult, but fun!
1,171 karma · joined September 29, 2012
Also, writing a solver for these things is also surprisingly difficult, but fun!
> The rules are a bit unintuitive. Definitely surprising that horizontal words don't have to be words.
You are not the first person to say this, and I am starting to agree. I think that more basic ruleset is more fun and far more intuitive. Especially given the current UI layout. I am going to spin up a new version with that ruleset I think.
Thanks!
Also, “on delete restrict” isn’t a bad policy either for some keys. Make deleting data difficult.
Also, 100ms is not fast.
It is incredible. He does an amazing job of starting from the basics and then diving deep. After going through the series I had a solid enough grasp on the language to use it for practical things.
https://www.youtube.com/watch?v=Vgu82wiiZ90&list=PLe7Ei6viL6...
When you are making a general purpose language that gets shipped to the masses, a core component of that thing you are making is the parsing. I'd say it is in your best interest to have complete control over how that works and be able to understand that well. That would mean putting in the work to make the parser yourself.
I don't just feel this way about building programming languages. I believe this is true for any kind of production level software that you write. It is important to maintain control and deep understanding of technologies that are core to your product. Building something from ready made components, while tempting, often ends badly.
I don't think I would use a parsing lib to build a general purpose programming language though. At least not one that I intended to ship.
If you're getting hung up on parsing and what not, you might be more successful using a parser generator. People hate them, often for good reason, but they do allow you to iterate quickly at first.
I haven't used it personally, but if you plan on using LLVM I hear that is a nightmare to use. Probably would also fit in to the "hardest", "tedious" and "least enjoyable" category for you too.
More broadly, what makes Godot in its current state unusable for your needs?
To some extent I agree with your mentality. I don't think we should treat work as anything other than that - trading your limited time for money. But you spend so much of it on this thing, work, that turning off your brain to engage in it seems just depressing.
That isn't to say that DDG is perfect, but for the times that it isn't perfect tacking an !g or !b to the end of the search does the job.
We are looking to hire an experienced software engineer to join our small team. We are a a bootstrapped startup company that is growing very quickly. We have a lot of big projects coming down the pike that we need help with.
Here is the link to the full job post if you'd like to learn more: https://weworkremotely.com/remote-jobs/insurance-toolkits-ll...
Feel free to reach out to me at frankie@fextoolkit.com
https://thekidshouldseethis.com/post/writer-automata-pierre-...
InsuranceToolkits is an underwriting, quoting, and sales tool suite for life insurance agents. We are looking to hire a backend developer to work on our underwriting and quoting engines.
Technologies (Relevant to this position): Python, Django + Django Rest Framework, Flask, Redis, Postgres
Other technologies that we use: TypeScript, Nuxt.js, Dart, Flutter (mobile)
We are a small but profitable startup company that is growing very quickly and we're looking to expand our team. We are on a mission to bring high quality software solutions to an industry that has been lacking them.
If you are interested in learning more, feel free to reach out to me at: frankie+jobs@insurancetoolkits.com
At least in ArcaneVM I think it's something like O(N^N) where N is the number of instructions in the program. The VM has no context on which instruction is supposed to be run when so every instruction needs to be "executed" at every step. It's absurdly slow and it doesn't help that the FHE algorithms themselves leave a lot to be desired when it comes to speed.
A few things have helped me. The first is that you need to embrace what you do and love what you do. It doesn't sound like you hate being a web developer, more that you feel you should be doing "harder" things. Web development is far more than CRUD apps, so it might be worth looking for another job that will challenge you more as a web developer.
The second thing is that you need to understand what you do _deeply_ instead of _broadly_. I have for a long time considered myself a generalist, but this has its drawbacks. When you really understand a tool set deeply and become an expert a lot of the lower level internals really reveal themselves. You end up learning things that you've always thought you wanted to learn in isolation, but instead there is now a useful context in which to learn them. Not to mention that this helps with the feeling of being "not so smart" because you will form informed opinions as a result of your deep level of understanding.
The last thing is that you do need to feed your curiosity and the only way to do that is through projects. You want to build a compiler, build an emulator, a game engine, a database, or an OS? You really just need to do it. I have dabbled in each one of these things. Some of which I got very deep into, others not so deep. Each time I learned a little bit more. The hardest part is picking a project and running with it, especially when there are so many different options, but it is the only way.
Sometimes it's important to take a step back and appreciate what you do. It's very easy to beat yourself up and compare yourself to others. If you really are unhappy with what you do, then you need to start deeply diving into something that you do find interesting. Nothing in this field is easy and it all takes time to gain any level of proficiency at.
Very inspiring!
With that being said, the job market is going to become much more brutal very soon, which slightly terrifies me... but I'd probably regret not at least taking a chance working towards my dream, even during these uncertain times. I did panic a bit when I got the news that I'd be losing my job, which lead to the frantic job applications and reaching out to my network. After I took a step back and thought about it though I was able to see this as an opportunity.
To anyone else out there who recently lost a job and is panicking, try to take a step back and evaluate your current situation. It might actually be setting yourself up for something better. If nothing else, take the time that you have to sharpen your skills or learn some new ones. Make the most of a bad situation.
I feel like we are approaching the problem of frontend development complexity the wrong way. These new frameworks and domain specific languages fail to cut through the complexity of the real problem and instead mask the complexity with shiny new frameworks. These frameworks still all suffer from the same problems.
There are deeper issues that need to be addressed. The fact that their landing page doesn’t work well on mobile is evidence of that. Assuming it was created using Mint.