St-Clock | 1 year ago | on: Are We PEP740 Yet?
St-Clock's comments
St-Clock | 3 years ago | on: We updated our RSA SSH host key
St-Clock | 3 years ago | on: Winter & Cold Weather EV Range Loss in 7,000 Cars
St-Clock | 4 years ago | on: AWS BugBust
The feedback was indeed similar to what standard linters and static analyzers can provide with more noise. I have no doubt they can improve their recommendations as they get more feedback and analyze more codebases, but we were not interested to pay to contribute.
We have had much more success with https://deepsource.io/ , which found real bugs and we generally agree with their recommendations. We are currently evaluating whether or not we will include this service as part of our process.
Deepsource is rule-based, but my understanding is that they are starting to use ML to rank recommendations.
St-Clock | 5 years ago | on: Cleaning Up Your Postgres Database
1. We insert the logs in the main database and periodically delete old logs. We can thus create the log in the same transaction as a record is created/updated/deleted. Yay atomicity!
2. The second database uses logical replication to receive new logs, but it only replicates INSERT operations so old logs are never deleted.
3. The application can show recent logs quickly (who updated the customer profile this week?) and if the user wants to dig deeper, we can query the slower log database but the user kind of expect that pulling the entire history of a record will take a bit longer than other operations.
St-Clock | 5 years ago | on: Vimflowy
I stopped using workflowy because it did not feel natural to edit a large amount of plain text outside of VIM.
St-Clock | 6 years ago | on: Service Quotas: View and manage your quotas for AWS services from one location
Additionally, it seems they did not import previous requests in their new request history.
St-Clock | 7 years ago | on: Ask HN: Who is hiring? (March 2019)
We are looking for a passionate developer who wants to join our software development team at Resulto. Your input will have a direct and measurable impact on the success of products frequently used by more 450 000 consumers.
You like to take initiative? You love web technologies but prefer to work your magic on the backend because that's your area of expertise. You want to work with experienced and dynamic colleagues? You are the perfect person to join our fantastic team!
To build our main product, we use:
- Backend: Python 3, Django, Django REST Framework et Celery - Frontend: ES6, Vue.js, Webpack, Bootstrap 4, SASS - Data: PostgreSQL, Memcached and Redis - Infrastructure: Ubuntu, Ansible, uWSGI, nginx, Terraform, Packer, AWS
We follow an agile development process and every person contributes to the continuous improvement of our processes and tools.
Working with Resulto has many perks:
- Contribute to the growth of a young company at a key stage of its evolution. - Relaxed work environment with a result-oriented and quality-driven culture. - Interesting technical challenges: software architecture, data mining, extreme configurability. - Flexible hours and telecommuting. - Competitive or friendly ping pong matches depending on your experience level! - And a lot more...
The ideal candidate will:
- Master a web programming language (+1 if you know Python, Ruby or Elixir) - Master a relational database (+1 if you know PostgreSQL or Oracle) and basic optimization and normalization techniques - Speak French or want to learn French
If you are interested, please email your CV to [email protected]
St-Clock | 7 years ago | on: WAL-G – fast archival and restoration for PostgreSQL
Andrey is also responsive if you encounter any issue and went to a lot of trouble to fix a hard to reproduce recovery issue we encountered.
St-Clock | 7 years ago | on: Ask HN: Who is hiring? (February 2019)
We are looking for a passionate developer who wants to join our software development team at Resulto. Your input will have a direct and measurable impact on the success of products frequently used by more 450 000 consumers.
You like to take initiative? You love web technologies but prefer to work your magic on the backend because that’s your area of expertise. You want to work with experienced and dynamic colleagues? You are the perfect person to join our fantastic team!
To build our main product, we use: * Backend: Python 3, Django, Django REST Framework et Celery * Frontend: ES6, Vue.js, Webpack, Bootstrap 4, SASS * Data: PostgreSQL, Memcached and Redis * Infrastructure: Ubuntu, Ansible, uWSGI, nginx, Terraform, Packer, AWS
We follow an agile development process and every person contributes to the continuous improvement of our processes and tools.
Working with Resulto has many perks: * Contribute to the growth of a young company at a key stage of its evolution. * Relaxed work environment with a result-oriented and quality-driven culture. * Interesting technical challenges: software architecture, data mining, extreme configurability. * Flexible hours and telecommuting. * Competitive or friendly ping pong matches depending on your experience level! * And a lot more...
The ideal candidate will: * Master a web programming language (+1 if you know Python, Ruby or Elixir) * Master a relational database (+1 if you know PostgreSQL or Oracle) and basic optimization and normalization techniques * Speak French or want to learn French
If you are interested, please email your CV to [email protected]
St-Clock | 7 years ago | on: Digital Ocean Managed Databases
[1] https://aws.amazon.com/blogs/aws/new-managed-databases-for-a...
St-Clock | 8 years ago | on: Ask HN: Who is hiring? (March 2018)
St-Clock | 8 years ago | on: Ask HN: Who is hiring? (March 2018)
We are looking for a passionate developer who wants to join our small software development team at Resulto in our office in Montreal. Your input will have a direct and measurable impact on the success of products used by more than 200 000 customers.
Our stack: * Backend: Python 3, Django, Django REST Framework et Celery
* Frontend: ES6, Vue.js, Webpack, Bootstrap 4, SASS
* Data/Cache: PostgreSQL, Memcached and Redis
* Infrastructure: Ubuntu, Ansible, uWSGI, nginx, Terraform, Packer, AWS
We follow an agile development process and every person contributes to the continuous improvement of our processes and tools.
Working with Resulto has many perks:
* Contribute to the growth of a startup at a key stage of its evolution.
* Work with a fantastic and experienced development team.
* Relaxed work environment with a result-oriented and quality-driven culture.
* Interesting technical challenges: software architecture, data mining, extreme configurability.
* Flexible hours and telecommuting.
* Competitive or friendly ping pong matches depending on your experience level!
* And a lot more...
The ideal candidate will:
* Have a good grasp SASS and JavaScript (+1 if you know Vue.js, React or Angular)
* Master one web programming language (+1 if you know Python, Ruby or Elixir)
* Have experience with a relational database (+1 if you know PostgreSQL or Oracle) and basic optimization and normalization techniques
* Have a good grasp of a distributed version control system (+1 if you know Git)
* Know how to use a server configuration tool (+1 if you know Ansible or Terraform)
* Speak French or want to learn French
Send your CV to [email protected] and mention HN for bonus points!
St-Clock | 8 years ago | on: Slack is the opposite of organizational memory
Another problem is that we would often end up replying to the wrong thread because of the way the general view is organized.
We are now trying Twist (https://twistapp.com) and it is a very good compromise between the efficiency of Zulip and the polished UI of Slack. The main advantage over Zulip is that you only see one complete thread at a time in the main column, but you can see the last message of each thread you've subscribed to in your inbox (second column): when you hit reply, you are certain that you are replying to the right thread.
St-Clock | 8 years ago | on: Tips for Building High-Quality Django Apps at Scale
This is too broad to be good advice. A typical solution to stale models is to increment a cache version key, effectively invalidating the old cache.
Version keys can be coarse- or fine-grained. For example, you may have one version key for the entire application (supported by Django by default) and one version key per model or application (you have to roll your own solution). If your app's models change, you can increment the app version key and the next time you try to fetch a model instance from the cache, you will miss and instead fetch the instance from the DB.
St-Clock | 9 years ago | on: Ask HN: Who is hiring? (April 2017)
Do you usually take initiative to suggest high-value improvements and keep up to date with best practices? Are you passionate with frontend technologies, but not afraid to dive into all the layers of a complex system? Do you want to participate in all phases of development and influence the business direction of a young and successful company? You are the perfect candidate and we would love to speak with you!
We are a bootstrapped company producing the leading loyalty and customer satisfaction platform in the powersport industry in Quebec. Your work would directly impact more than 200 000 customers and users.
We at Resulto strongly believes that bringing new interns and employees to our team is a learning and growing opportunity for both sides. If this sounds interesting to you, email us at [email protected]
St-Clock | 9 years ago | on: Cloud Hosting Showdown: DO vs. Linode vs. Vultr vs. OVH vs. Scaleway
Moreover, to me, regular VPS == openvz and not hourly billing (openvz would also disqualify ssdnodes).
St-Clock | 9 years ago | on: Summary of the Amazon S3 Service Disruption
From a software development perspective, it makes sense to reuse S3 and rely on it internally if you need object storage, but from an ops perspective, it means that S3 is now a single point of failure and that SES's reliability will always be capped by S3's reliability. From a customer perspective, the hard dependency between SES and S3 is not obvious and is disappointing.
The whole internet was talking about S3 when the AWS status dashboard did not show any outage, but very few people mentioned other services such as SES. Next time we encounter errors with SES, should we check for hints of S3 outage before everything else? Should we also check for EC2 outage?
St-Clock | 9 years ago | on: Ask HN: Is S3 down?
St-Clock | 9 years ago | on: Postmodern Error Handling in Python 3.6
I can speak for experience. Py4J is on that list and getting maintainers is very difficult (for various reasons). Packaging is also not something that naturally attracts contributions.