I was about to setup a subscription, but haven't found my language in Interface Language settings. Why there is no translation for widely used languages like Chinese, but avaiable for super rare languages like "Luxembourgish"?
I guess when I initially wrote I was thinking more from the position "обращайся" which has more interact flavor and made more sense vis a vis attention.
I see many comments on broken key combinations. Obviously, we need to somehow overcome a UI/UX limitations of the applications that run inside a browser if we're moving into browsers with the consumer apps. I wrote a dedicated article on this: https://database.blog/trello-hot-keys/
In our local IT community chat, we have a funny tradition of posting bathroom review videos from different IT companies. From what I've seen, turns out that your assumption is totally true.
Hi! I am an experienced senior developer currently working full-time on bootstrapping my own saas startup. I am looking for part-time contract jobs to support my development. I can help you:
* Build working MVP in a very short time
* Design and develop both front- and back-end parts of the service
* Speed up development process and help ship features faster
This is not a straight guide to assembly, but imho a very useful book to start with low-level assembly code. It's very clear and easy understandable reading to dive into low level code. There are lots of examples and not only for x86, but also ARM. http://beginners.re
When considering using ORM we need to answer simple questions: does it help to decrease code size? In most cases ORM code is same size as SQL query. Secondly, does it hide complexity? No, it just adds up one more layer that in fact increases complexity and makes it harder to debug. Finally, does it protect us from errors or impoves code quality? This is rarely the case.
Instead of using ORM I prefer moving data retrieval code to database layer with help of views. There is also updatable views that we can use to simplify database updates on code side and sometimes avoid using transactions. Separation of code and data logic is great concern when deciding to implement ORM. Nowdays database are very smart and convinient so there is no need to use ORM.
In most cases its smaller (in the Django ORM anyway).
myobject, created = MyObject.objects.get_or_create(field1='1' , field2=field2)
That would take a number of lines. One query to check if the object exists, another to create it / retrieve it, plus application code to deal with that SQL.
Ok, for this particular example, is operation wrapped in transaction? How will code evalute if we need to check some condition on field2 and occasionally update it?
