Saturday, February 8, 2025

Re: Remote Full Stack Developer 85k-125k at Redwith Technologies LLC

not using chatgpt to generate long essays that is even hard to read.

here's my portfolio: https://www.basith.me/
I write on LinkedIn:  https://www.linkedin.com/in/muhammedbasith

really looking forward for this if you are looking for a passionate swe.





On Sat, 8 Feb 2025 at 22:12, emma sie <emmasie010@gmail.com> wrote:
I am not a developer but a network engineer. but i can take experience to learn and work for you


Le mer. 15 janv. 2025 à 19:17, Allarassem Maxime <allarassemmaxwell@gmail.com> a écrit :

I hope this email finds you well. I am writing to express my interest in the Full Stack Developer position at Redwith Technologies. With a strong background in Python/Django and front-end technologies, along with experience in building scalable web applications and APIs, I am excited about the opportunity to contribute to your innovative team.

I have attached my resume for your review, and I am eager to discuss how my skills and experience align with the requirements of this role. Thank you for considering my application.

I look forward to the possibility of contributing to Redwith Technologies and being a part of the exciting work you're doing in the real estate tech industry.

Best regards,
Allarassem Maxime
+254704205757


On Tue, Jan 14, 2025 at 7:45 PM Axel Teddy DERO <teddydero@gmail.com> wrote:


Le mar. 14 janv. 2025 à 09:24, kumbhaj shukla <kumbhajs0@gmail.com> a écrit :

Hi sir,
Here is my resume.


On Tue, 14 Jan, 2025, 3:51 am Otecina, <otecina500@gmail.com> wrote:

Greetings dear recruiter, I am interested in this vacancy. I noticed that I have the skills that are being requested, however I am attaching my CV below.

Best regards


On Mon, Jan 13, 2025, 5:51 PM Miracle <collinsalex50@gmail.com> wrote:
I'm qualified and interested in this position.

Please find my resume attached

On Mon, 13 Jan 2025, 4:47 pm sertaç c, <prof.math@gmail.com> wrote:

POSITION: Full Stack Developer

LOCATION: New Haven, CT (Hybrid/Remote flexibility available)

ABOUT REDWITH TECHNOLOGIES At Redwith Technologies, we're dedicated to building innovative software solutions that revolutionize residential real estate technology. As part of our growing team, you'll be involved in creating and optimizing web applications that drive the industry forward. We value collaboration, creativity, and delivering high-impact solutions that transform the way real estate professionals and Multiple Listing Services (MLSs) operate and serve their subscribers and consumers alike. We are looking for a highly motivated and skilled Full Stack Developer to join our team. This is an exciting opportunity for someone passionate about tackling complex technical challenges, from requirements analysis to system design and deployment. As a Full Stack Developer at Redwith, you will have the chance to work on a diverse set of projects, including designing scalable solutions, optimizing performance, and ensuring the seamless integration of systems. You will play a key role in shaping our web applications and APIs, while contributing to an agile and collaborative development environment.

KEY RESPONSIBILITIES

  • Develop and maintain high-quality, scalable web applications and APIs using Python/Django.
  • Collaborate with product managers, designers, and other developers to deliver exceptional software solutions.
  • Work through the full software development lifecycle, including requirements gathering, system design, development, and deployment.
  • Troubleshoot and optimize performance, ensuring the application meets functional and non-functional requirements.
  • Contribute to the evolution of development best practices and ensure the team follows an agile development process.
  • Create and maintain clear, concise technical documentation to support the development lifecycle.

IDEAL SKILLS & EXPERIENCE:

  • Proficiency in Python and Django for backend development.
  • Strong experience with JavaScript, HTML/CSS, and modern front-end frameworks.
  • Knowledge of PostgreSQL and Redis for database management and caching.
  • Familiarity with Git for version control and collaboration.
  • Solid understanding of DevOps practices, cloud environments, and continuous integration/deployment (CI/CD).
  • Experience with agile methodologies and the ability to work effectively in a collaborative environment.
  • Strong communication skills, both written and verbal, with the ability to document technical processes clearly.

WHAT WE OFFER:

  • Competitive salary commensurate with skill level/experience.
  • Benefits package including paid time off, healthcare benefits, and supplemental benefits.
  • Professional development opportunities and a chance to grow your career in a forward-thinking company.
  • Collaborative work culture with a focus on innovation, personal and technical development/growth.
  • Flexible working arrangements, including hybrid and remote options.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/d345b524-9648-4fe5-b169-83438de56311n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CADZv-jDvD99yxfA9c2mvArNiaKWTbfQMBmAbRqa%3DCPUfMDm%3DMg%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CANdWVZbSk9vZM-XywtzdcEoULOcrF0uMrVEvW_g-8fsJSDFvdA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CAPjc%3DUV_3W1acnY9anzFKJ7LdDuhZDoq6wfCJe-hu%3Dy9ide%3D7A%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CALtkRM8Ye8_VfrRX6kkUSBU7HYgNbtW9yEgsw_5%3DQYxqto30NA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CACF1NJyVQa0YqeemNeKSw092t%2Bmck-jebGNyf8O8wvnY1c7qcA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CAFr75P6yQWNftQrChgtjJbQc%3D7KYA%2BdSaebNyqbL8jeNrmoeyA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CAADw1szEDSm%3DW1tX%2B%2BheAwzTwkOw-33tQ40Q3LsN7snmg1gUzQ%40mail.gmail.com.

Friday, February 7, 2025

Re: Django developer required- Work from Home

Proposal for Expert Django Developer Engagement

I hope this message finds you well.
I am writing to express my strong interest in the opportunity to lead
your website development project as an expert Django developer on a
contract/hourly basis.
With extensive experience in Django and web development, I am
confident that I can provide the leadership and technical expertise
necessary to ensure the success of your project.

Why Choose Me:

Expertise in Django: With 10 years of experience, I've developed
robust web applications using Django

Strong Technical Skills: I'm proficient in Python, JavaScript, and
front-end technologies (HTML, CSS).
I excel in integrating RESTful APIs and have experience with databases
like PostgreSQL and MySQL.

Team Leadership: I've led development teams, promoting best practices
and effective collaboration through clear communication and agile
methodologies.

Problem-Solving: I thrive in challenging environments, committed to
finding innovative and efficient solutions that meet both technical
and business needs.

Proposed Engagement:

Availability: I'm available part-time/full-time, specific hours and
can adjust my hours to align with your team's schedule.

Rates: My hourly rate is30$, reflecting the quality of work I deliver.

Next Steps: I'd love to discuss your project further. Are you
available for a quick call or meeting this week?

Thank you for considering my proposal.
I'm excited about the opportunity to collaborate and contribute to
your project's success.
Looking forward to your response!

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CAJyUeCRZvgXXpvrnG10d4DO1R_MP%3DXJtk1E68QOB7AHV%2BVqREA%40mail.gmail.com.

Re: Django developer required- Work from Home

Hello, I'm interested
Regards,
Mark

On Wed, Feb 5, 2025 at 10:27 PM Nilesh Mishra <k.nileshmishra@gmail.com> wrote:
We require expert django developer on contract/hourly basis to lead our team for website development.

Required skill set

Python
Django
Mongodb
React js

Please send your CV to


Regards
Nilesh Mishra 
Whatsapp:- +91-82796-73706

On Thu, Jan 30, 2025, 01:34 Alexei Ramotar <alexei.ramotar@gmail.com> wrote:

I'd just give the columns generic names and let react handle the names you want to display which is probably based on dates or something cyclical. Otherwise it seems like too much overhead in renaming fields and migration.


On Wed, Jan 29, 2025, 2:56 PM 'Ryan Nowakowski' via Django users <django-users@googlegroups.com> wrote:

On 1/27/25 7:41 AM, Mayank Prajapati wrote:
> I am making a full stack project with JavaScript and react for front end , Postgre SQL for database and Django for backend and Django rest framework for APIs. So in models.py file there's one field which is to be removed and another field is to be added at the end. This process has to be done once daily at specific time. For example, assume there are five fields in my models i.e. A,B,C,D and E. At some specific time field B will be removed and new field E will be added after D, again same process will repeat next day field C will be removed and new field F will be added after E. I can implement this process through python file handling and "with" method.
>
> So my question is, should i implement this process in my Django project? Will this process work efficiently in production environment?
>

When you say "field" are these FileFields <https://docs.djangoproject.com/en/5.1/ref/models/fields/#filefield>? And when you say "removed" and "added", are you talking about actually removing the field from the model(via migrations <https://docs.djangoproject.com/en/5.1/topics/migrations/>) or setting that field to "None"(null) when you "remove" it?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/B1F2C8F6-766A-4515-ADEC-C72D59866E71%40fattuba.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CACCvK-vi3ooiMfKAGpMYyme4c2jA1fxbvY3HD0tdBRn7oc%2Bx%2BQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CANGWp6zEwcKGwwbj-JxNTDmMM-d7ivJFMJbQagR0JKKg600C2g%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CAFm0m6SDqETb9njxbgvTn3WOaNrvOAMK1J1PkJtZDVyec1SQAQ%40mail.gmail.com.

Wednesday, February 5, 2025

Django developer required- Work from Home

We require expert django developer on contract/hourly basis to lead our team for website development.

Required skill set

Python
Django
Mongodb
React js

Please send your CV to


Regards
Nilesh Mishra 
Whatsapp:- +91-82796-73706

On Thu, Jan 30, 2025, 01:34 Alexei Ramotar <alexei.ramotar@gmail.com> wrote:

I'd just give the columns generic names and let react handle the names you want to display which is probably based on dates or something cyclical. Otherwise it seems like too much overhead in renaming fields and migration.


On Wed, Jan 29, 2025, 2:56 PM 'Ryan Nowakowski' via Django users <django-users@googlegroups.com> wrote:

On 1/27/25 7:41 AM, Mayank Prajapati wrote:
> I am making a full stack project with JavaScript and react for front end , Postgre SQL for database and Django for backend and Django rest framework for APIs. So in models.py file there's one field which is to be removed and another field is to be added at the end. This process has to be done once daily at specific time. For example, assume there are five fields in my models i.e. A,B,C,D and E. At some specific time field B will be removed and new field E will be added after D, again same process will repeat next day field C will be removed and new field F will be added after E. I can implement this process through python file handling and "with" method.
>
> So my question is, should i implement this process in my Django project? Will this process work efficiently in production environment?
>

When you say "field" are these FileFields <https://docs.djangoproject.com/en/5.1/ref/models/fields/#filefield>? And when you say "removed" and "added", are you talking about actually removing the field from the model(via migrations <https://docs.djangoproject.com/en/5.1/topics/migrations/>) or setting that field to "None"(null) when you "remove" it?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/B1F2C8F6-766A-4515-ADEC-C72D59866E71%40fattuba.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CACCvK-vi3ooiMfKAGpMYyme4c2jA1fxbvY3HD0tdBRn7oc%2Bx%2BQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CANGWp6zEwcKGwwbj-JxNTDmMM-d7ivJFMJbQagR0JKKg600C2g%40mail.gmail.com.

Tuesday, February 4, 2025

Re: File handling in Django

Je suis disposé, crache le marché 

Le mar. 4 févr. 2025, 15:25, Idohou Sandé Augustin <asidev7@gmail.com> a écrit :

I'm looking for back end developer Django


Le mar. 4 févr. 2025, 06:03, Agar Joshua <joshuaagarjj@gmail.com> a écrit :
Hi I agree with alexei.ramotar@gmail.com renaming fields and doing migrations is definitely not the most optimal solution. I suggest you have generic names. Anything variable mostly ends up being a field on a table or a table, depending on your use case. I hope you figured that out though?

On Wed, Jan 29, 2025 at 11:05 PM Alexei Ramotar <alexei.ramotar@gmail.com> wrote:

I'd just give the columns generic names and let react handle the names you want to display which is probably based on dates or something cyclical. Otherwise it seems like too much overhead in renaming fields and migration.


On Wed, Jan 29, 2025, 2:56 PM 'Ryan Nowakowski' via Django users <django-users@googlegroups.com> wrote:

On 1/27/25 7:41 AM, Mayank Prajapati wrote:
> I am making a full stack project with JavaScript and react for front end , Postgre SQL for database and Django for backend and Django rest framework for APIs. So in models.py file there's one field which is to be removed and another field is to be added at the end. This process has to be done once daily at specific time. For example, assume there are five fields in my models i.e. A,B,C,D and E. At some specific time field B will be removed and new field E will be added after D, again same process will repeat next day field C will be removed and new field F will be added after E. I can implement this process through python file handling and "with" method.
>
> So my question is, should i implement this process in my Django project? Will this process work efficiently in production environment?
>

When you say "field" are these FileFields <https://docs.djangoproject.com/en/5.1/ref/models/fields/#filefield>? And when you say "removed" and "added", are you talking about actually removing the field from the model(via migrations <https://docs.djangoproject.com/en/5.1/topics/migrations/>) or setting that field to "None"(null) when you "remove" it?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/B1F2C8F6-766A-4515-ADEC-C72D59866E71%40fattuba.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CACCvK-vi3ooiMfKAGpMYyme4c2jA1fxbvY3HD0tdBRn7oc%2Bx%2BQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CALHJg5%2BPWQXN3Wxnse8LZu%3Dm-1wgZ3S-EpCUk5hajMKR%3DPq3OA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CA%2BbeU1Oa6-CL%3D4LBkiOVVXE9kEfqsBYQvLwH0dhsXFDD2Vei6w%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CA%2BGQzJO8DyBDNJ%2BQcj-pDJ08tKTVoGdFNn0YzM0hM-gNCYOTOQ%40mail.gmail.com.

Re: File handling in Django

I'm looking for back end developer Django


Le mar. 4 févr. 2025, 06:03, Agar Joshua <joshuaagarjj@gmail.com> a écrit :
Hi I agree with alexei.ramotar@gmail.com renaming fields and doing migrations is definitely not the most optimal solution. I suggest you have generic names. Anything variable mostly ends up being a field on a table or a table, depending on your use case. I hope you figured that out though?

On Wed, Jan 29, 2025 at 11:05 PM Alexei Ramotar <alexei.ramotar@gmail.com> wrote:

I'd just give the columns generic names and let react handle the names you want to display which is probably based on dates or something cyclical. Otherwise it seems like too much overhead in renaming fields and migration.


On Wed, Jan 29, 2025, 2:56 PM 'Ryan Nowakowski' via Django users <django-users@googlegroups.com> wrote:

On 1/27/25 7:41 AM, Mayank Prajapati wrote:
> I am making a full stack project with JavaScript and react for front end , Postgre SQL for database and Django for backend and Django rest framework for APIs. So in models.py file there's one field which is to be removed and another field is to be added at the end. This process has to be done once daily at specific time. For example, assume there are five fields in my models i.e. A,B,C,D and E. At some specific time field B will be removed and new field E will be added after D, again same process will repeat next day field C will be removed and new field F will be added after E. I can implement this process through python file handling and "with" method.
>
> So my question is, should i implement this process in my Django project? Will this process work efficiently in production environment?
>

When you say "field" are these FileFields <https://docs.djangoproject.com/en/5.1/ref/models/fields/#filefield>? And when you say "removed" and "added", are you talking about actually removing the field from the model(via migrations <https://docs.djangoproject.com/en/5.1/topics/migrations/>) or setting that field to "None"(null) when you "remove" it?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/B1F2C8F6-766A-4515-ADEC-C72D59866E71%40fattuba.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CACCvK-vi3ooiMfKAGpMYyme4c2jA1fxbvY3HD0tdBRn7oc%2Bx%2BQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CALHJg5%2BPWQXN3Wxnse8LZu%3Dm-1wgZ3S-EpCUk5hajMKR%3DPq3OA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CA%2BbeU1Oa6-CL%3D4LBkiOVVXE9kEfqsBYQvLwH0dhsXFDD2Vei6w%40mail.gmail.com.

Re: File handling in Django

Implémenter un processus de modification quotidienne des champs de modèle dans un projet Django peut être complexe, mais c'est faisable. Voici quelques points à considérer pour garantir que le processus fonctionne efficacement dans un environnement de production :

✅Planification des tâches:
Pour automatiser la suppression et l'ajout de champs à une heure précise chaque jour, vous pouvez utiliser un planificateur de tâches comme **Celery** avec Django. Celery vous permet de gérer les tâches périodiques de manière efficace. Vous pouvez également utiliser **Django-cron** pour exécuter des tâches planifiées.

✅Gestion des migrations
Chaque fois que vous modifiez un modèle Django, vous devez créer et appliquer des migrations pour mettre à jour la base de données. Vous pouvez automatiser ce processus en utilisant des scripts qui exécutent les commandes `makemigrations` et `migrate` de Django.

### Exemple de script pour les migrations
Voici un script de ce que j'avais utilisé  dans mon application des migrations :
```python
import os
import django
from django.core.management import call_command
from datetime import datetime

# Configurer Django
os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'mon_projet.settings')
django.setup()

# Fonction pour mettre à jour les modèles
def update_models():
    # Supprimer le champ B
    call_command('makemigrations', 'mon_app', name='remove_field_b')
    call_command('migrate', 'mon_app')

    # Ajouter le nouveau champ E
    call_command('makemigrations', 'mon_app', name='add_field_e')
    call_command('migrate', 'mon_app')

# Planifier l'exécution quotidienne
if datetime.now().hour == 2:  # Remplacez 2 par l'heure souhaitée
    update_models()
```


Le mar. 4 févr. 2025, 06:03, Agar Joshua <joshuaagarjj@gmail.com> a écrit :
Hi I agree with alexei.ramotar@gmail.com renaming fields and doing migrations is definitely not the most optimal solution. I suggest you have generic names. Anything variable mostly ends up being a field on a table or a table, depending on your use case. I hope you figured that out though?

On Wed, Jan 29, 2025 at 11:05 PM Alexei Ramotar <alexei.ramotar@gmail.com> wrote:

I'd just give the columns generic names and let react handle the names you want to display which is probably based on dates or something cyclical. Otherwise it seems like too much overhead in renaming fields and migration.


On Wed, Jan 29, 2025, 2:56 PM 'Ryan Nowakowski' via Django users <django-users@googlegroups.com> wrote:

On 1/27/25 7:41 AM, Mayank Prajapati wrote:
> I am making a full stack project with JavaScript and react for front end , Postgre SQL for database and Django for backend and Django rest framework for APIs. So in models.py file there's one field which is to be removed and another field is to be added at the end. This process has to be done once daily at specific time. For example, assume there are five fields in my models i.e. A,B,C,D and E. At some specific time field B will be removed and new field E will be added after D, again same process will repeat next day field C will be removed and new field F will be added after E. I can implement this process through python file handling and "with" method.
>
> So my question is, should i implement this process in my Django project? Will this process work efficiently in production environment?
>

When you say "field" are these FileFields <https://docs.djangoproject.com/en/5.1/ref/models/fields/#filefield>? And when you say "removed" and "added", are you talking about actually removing the field from the model(via migrations <https://docs.djangoproject.com/en/5.1/topics/migrations/>) or setting that field to "None"(null) when you "remove" it?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/B1F2C8F6-766A-4515-ADEC-C72D59866E71%40fattuba.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CACCvK-vi3ooiMfKAGpMYyme4c2jA1fxbvY3HD0tdBRn7oc%2Bx%2BQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CALHJg5%2BPWQXN3Wxnse8LZu%3Dm-1wgZ3S-EpCUk5hajMKR%3DPq3OA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CA%2BGQzJMFKK6ejB4vXvcM%3DTEnGWreRi6gwYw6ZQ3R4HBgGO4aZg%40mail.gmail.com.

Monday, February 3, 2025

Re: File handling in Django

Mayank 

I think you should not delete and add  the fields rather make them one consistent model so that while reporting or may be during data analytics that will play big role since it's just date field. 

Otherwise changing the model may need migration which is like adding an extra process 

All the best


Best Regards

Sidhaarrth S Nayyar

R S Infomedia And Films Pvt Ltd. | WZ-79C/6, First floor, Lane no 7A, Main Bharti College Road, Virender Nagar, Janak Puri, New Delhi – 1100 058, India.
+91 9811222863 (primary), 8076606202 |  +91 11 25546949 |  IMDB | Linkedin | Google Hangout | Skype | www.rsifpl.com | www.rsproduction.com | SHOWREEL |


On Wed, 29 Jan 2025 at 16:06, Mayank Prajapati <mayankprajapati1399@gmail.com> wrote:

I am making train ticket booking project in which I have to keep record of number of tickets booked and remaining seats for 60 days from today. So as the day passes , passed date field have to be removed and new date after 59 days from today has to be added.


On Wed, 29 Jan 2025, 12:24 pm Agar Joshua, <joshuaagarjj@gmail.com> wrote:
This is an interesting implementation. I am curious, what are you trying to achieve that necessitates adding and removing fields? And wouldnt that be solved better with some table relationship instead?

On Tue, Jan 28, 2025 at 1:33 AM Mayank Prajapati <mayankprajapati1399@gmail.com> wrote:
I am making a full stack project with JavaScript and react for front end , Postgre SQL for database and Django for backend and Django rest framework for APIs. So in models.py file there's one field which is to be removed and another field is to be added at the end. This process has to be done once daily at specific time. For example, assume there are five fields in my models i.e. A,B,C,D and E. At some specific time field B will be removed and new field E will be added after D, again same process will repeat next day field C will be removed and new field F will be added after E. I can implement this process through python file handling and "with" method. 

So my question is, should i implement this process in my Django project? Will this process work efficiently in production environment?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/75091646-157a-4b2e-8aa0-0c05b2d50b0fn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CALHJg5%2BRzLrFE0%3DAro_ByQe3nJixBMLObdfVQNsBoeTsRibLhQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CAEn_UdWRSHSvBVtvpQ3QfENwbFtX7zA2i2p4z9_ye2vNd4Mqhg%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CAN__fS7Msoy7b6%2BkDDGtNPPdJM1iUAnx6gsV-BSrfv5u1HDX8g%40mail.gmail.com.

Re: File handling in Django

Hi I agree with alexei.ramotar@gmail.com renaming fields and doing migrations is definitely not the most optimal solution. I suggest you have generic names. Anything variable mostly ends up being a field on a table or a table, depending on your use case. I hope you figured that out though?

On Wed, Jan 29, 2025 at 11:05 PM Alexei Ramotar <alexei.ramotar@gmail.com> wrote:

I'd just give the columns generic names and let react handle the names you want to display which is probably based on dates or something cyclical. Otherwise it seems like too much overhead in renaming fields and migration.


On Wed, Jan 29, 2025, 2:56 PM 'Ryan Nowakowski' via Django users <django-users@googlegroups.com> wrote:

On 1/27/25 7:41 AM, Mayank Prajapati wrote:
> I am making a full stack project with JavaScript and react for front end , Postgre SQL for database and Django for backend and Django rest framework for APIs. So in models.py file there's one field which is to be removed and another field is to be added at the end. This process has to be done once daily at specific time. For example, assume there are five fields in my models i.e. A,B,C,D and E. At some specific time field B will be removed and new field E will be added after D, again same process will repeat next day field C will be removed and new field F will be added after E. I can implement this process through python file handling and "with" method.
>
> So my question is, should i implement this process in my Django project? Will this process work efficiently in production environment?
>

When you say "field" are these FileFields <https://docs.djangoproject.com/en/5.1/ref/models/fields/#filefield>? And when you say "removed" and "added", are you talking about actually removing the field from the model(via migrations <https://docs.djangoproject.com/en/5.1/topics/migrations/>) or setting that field to "None"(null) when you "remove" it?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/B1F2C8F6-766A-4515-ADEC-C72D59866E71%40fattuba.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CACCvK-vi3ooiMfKAGpMYyme4c2jA1fxbvY3HD0tdBRn7oc%2Bx%2BQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CALHJg5%2BPWQXN3Wxnse8LZu%3Dm-1wgZ3S-EpCUk5hajMKR%3DPq3OA%40mail.gmail.com.

Friday, January 31, 2025

Re: Remote Full Stack Developer 85k-125k at Redwith Technologies LLC

I am not a developer but a network engineer. but i can take experience to learn and work for you


Le mer. 15 janv. 2025 à 19:17, Allarassem Maxime <allarassemmaxwell@gmail.com> a écrit :

I hope this email finds you well. I am writing to express my interest in the Full Stack Developer position at Redwith Technologies. With a strong background in Python/Django and front-end technologies, along with experience in building scalable web applications and APIs, I am excited about the opportunity to contribute to your innovative team.

I have attached my resume for your review, and I am eager to discuss how my skills and experience align with the requirements of this role. Thank you for considering my application.

I look forward to the possibility of contributing to Redwith Technologies and being a part of the exciting work you're doing in the real estate tech industry.

Best regards,
Allarassem Maxime
+254704205757


On Tue, Jan 14, 2025 at 7:45 PM Axel Teddy DERO <teddydero@gmail.com> wrote:


Le mar. 14 janv. 2025 à 09:24, kumbhaj shukla <kumbhajs0@gmail.com> a écrit :

Hi sir,
Here is my resume.


On Tue, 14 Jan, 2025, 3:51 am Otecina, <otecina500@gmail.com> wrote:

Greetings dear recruiter, I am interested in this vacancy. I noticed that I have the skills that are being requested, however I am attaching my CV below.

Best regards


On Mon, Jan 13, 2025, 5:51 PM Miracle <collinsalex50@gmail.com> wrote:
I'm qualified and interested in this position.

Please find my resume attached

On Mon, 13 Jan 2025, 4:47 pm sertaç c, <prof.math@gmail.com> wrote:

POSITION: Full Stack Developer

LOCATION: New Haven, CT (Hybrid/Remote flexibility available)

ABOUT REDWITH TECHNOLOGIES At Redwith Technologies, we're dedicated to building innovative software solutions that revolutionize residential real estate technology. As part of our growing team, you'll be involved in creating and optimizing web applications that drive the industry forward. We value collaboration, creativity, and delivering high-impact solutions that transform the way real estate professionals and Multiple Listing Services (MLSs) operate and serve their subscribers and consumers alike. We are looking for a highly motivated and skilled Full Stack Developer to join our team. This is an exciting opportunity for someone passionate about tackling complex technical challenges, from requirements analysis to system design and deployment. As a Full Stack Developer at Redwith, you will have the chance to work on a diverse set of projects, including designing scalable solutions, optimizing performance, and ensuring the seamless integration of systems. You will play a key role in shaping our web applications and APIs, while contributing to an agile and collaborative development environment.

KEY RESPONSIBILITIES

  • Develop and maintain high-quality, scalable web applications and APIs using Python/Django.
  • Collaborate with product managers, designers, and other developers to deliver exceptional software solutions.
  • Work through the full software development lifecycle, including requirements gathering, system design, development, and deployment.
  • Troubleshoot and optimize performance, ensuring the application meets functional and non-functional requirements.
  • Contribute to the evolution of development best practices and ensure the team follows an agile development process.
  • Create and maintain clear, concise technical documentation to support the development lifecycle.

IDEAL SKILLS & EXPERIENCE:

  • Proficiency in Python and Django for backend development.
  • Strong experience with JavaScript, HTML/CSS, and modern front-end frameworks.
  • Knowledge of PostgreSQL and Redis for database management and caching.
  • Familiarity with Git for version control and collaboration.
  • Solid understanding of DevOps practices, cloud environments, and continuous integration/deployment (CI/CD).
  • Experience with agile methodologies and the ability to work effectively in a collaborative environment.
  • Strong communication skills, both written and verbal, with the ability to document technical processes clearly.

WHAT WE OFFER:

  • Competitive salary commensurate with skill level/experience.
  • Benefits package including paid time off, healthcare benefits, and supplemental benefits.
  • Professional development opportunities and a chance to grow your career in a forward-thinking company.
  • Collaborative work culture with a focus on innovation, personal and technical development/growth.
  • Flexible working arrangements, including hybrid and remote options.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/d345b524-9648-4fe5-b169-83438de56311n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CADZv-jDvD99yxfA9c2mvArNiaKWTbfQMBmAbRqa%3DCPUfMDm%3DMg%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CANdWVZbSk9vZM-XywtzdcEoULOcrF0uMrVEvW_g-8fsJSDFvdA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CAPjc%3DUV_3W1acnY9anzFKJ7LdDuhZDoq6wfCJe-hu%3Dy9ide%3D7A%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CALtkRM8Ye8_VfrRX6kkUSBU7HYgNbtW9yEgsw_5%3DQYxqto30NA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CACF1NJyVQa0YqeemNeKSw092t%2Bmck-jebGNyf8O8wvnY1c7qcA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CAFr75P6yQWNftQrChgtjJbQc%3D7KYA%2BdSaebNyqbL8jeNrmoeyA%40mail.gmail.com.

Wednesday, January 29, 2025

Re: File handling in Django

I'd just give the columns generic names and let react handle the names you want to display which is probably based on dates or something cyclical. Otherwise it seems like too much overhead in renaming fields and migration.


On Wed, Jan 29, 2025, 2:56 PM 'Ryan Nowakowski' via Django users <django-users@googlegroups.com> wrote:

On 1/27/25 7:41 AM, Mayank Prajapati wrote:
> I am making a full stack project with JavaScript and react for front end , Postgre SQL for database and Django for backend and Django rest framework for APIs. So in models.py file there's one field which is to be removed and another field is to be added at the end. This process has to be done once daily at specific time. For example, assume there are five fields in my models i.e. A,B,C,D and E. At some specific time field B will be removed and new field E will be added after D, again same process will repeat next day field C will be removed and new field F will be added after E. I can implement this process through python file handling and "with" method.
>
> So my question is, should i implement this process in my Django project? Will this process work efficiently in production environment?
>

When you say "field" are these FileFields <https://docs.djangoproject.com/en/5.1/ref/models/fields/#filefield>? And when you say "removed" and "added", are you talking about actually removing the field from the model(via migrations <https://docs.djangoproject.com/en/5.1/topics/migrations/>) or setting that field to "None"(null) when you "remove" it?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/B1F2C8F6-766A-4515-ADEC-C72D59866E71%40fattuba.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CACCvK-vi3ooiMfKAGpMYyme4c2jA1fxbvY3HD0tdBRn7oc%2Bx%2BQ%40mail.gmail.com.

Re: File handling in Django


On 1/27/25 7:41 AM, Mayank Prajapati wrote:
> I am making a full stack project with JavaScript and react for front end , Postgre SQL for database and Django for backend and Django rest framework for APIs. So in models.py file there's one field which is to be removed and another field is to be added at the end. This process has to be done once daily at specific time. For example, assume there are five fields in my models i.e. A,B,C,D and E. At some specific time field B will be removed and new field E will be added after D, again same process will repeat next day field C will be removed and new field F will be added after E. I can implement this process through python file handling and "with" method.
>
> So my question is, should i implement this process in my Django project? Will this process work efficiently in production environment?
>

When you say "field" are these FileFields <https://docs.djangoproject.com/en/5.1/ref/models/fields/#filefield>? And when you say "removed" and "added", are you talking about actually removing the field from the model(via migrations <https://docs.djangoproject.com/en/5.1/topics/migrations/>) or setting that field to "None"(null) when you "remove" it?

RE: File handling in Django

Hi, When changing the model, you will need to migrate.

Rather update the past_date field with the newdate etc..

 

 

Johannes

 

 

From: django-users@googlegroups.com <django-users@googlegroups.com> On Behalf Of Mayank Prajapati
Sent: Wednesday, January 29, 2025 12:34 PM
To: django-users@googlegroups.com
Subject: Re: File handling in Django

 

I am making train ticket booking project in which I have to keep record of number of tickets booked and remaining seats for 60 days from today. So as the day passes , passed date field have to be removed and new date after 59 days from today has to be added.

 

On Wed, 29 Jan 2025, 12:24 pm Agar Joshua, <joshuaagarjj@gmail.com> wrote:

This is an interesting implementation. I am curious, what are you trying to achieve that necessitates adding and removing fields? And wouldnt that be solved better with some table relationship instead?

 

On Tue, Jan 28, 2025 at 1:33 AM Mayank Prajapati <mayankprajapati1399@gmail.com> wrote:

I am making a full stack project with JavaScript and react for front end , Postgre SQL for database and Django for backend and Django rest framework for APIs. So in models.py file there's one field which is to be removed and another field is to be added at the end. This process has to be done once daily at specific time. For example, assume there are five fields in my models i.e. A,B,C,D and E. At some specific time field B will be removed and new field E will be added after D, again same process will repeat next day field C will be removed and new field F will be added after E. I can implement this process through python file handling and "with" method. 

 

So my question is, should i implement this process in my Django project? Will this process work efficiently in production environment?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/75091646-157a-4b2e-8aa0-0c05b2d50b0fn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CALHJg5%2BRzLrFE0%3DAro_ByQe3nJixBMLObdfVQNsBoeTsRibLhQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CAEn_UdWRSHSvBVtvpQ3QfENwbFtX7zA2i2p4z9_ye2vNd4Mqhg%40mail.gmail.com.


Virus-free.www.avg.com

Re: File handling in Django

I am making train ticket booking project in which I have to keep record of number of tickets booked and remaining seats for 60 days from today. So as the day passes , passed date field have to be removed and new date after 59 days from today has to be added.


On Wed, 29 Jan 2025, 12:24 pm Agar Joshua, <joshuaagarjj@gmail.com> wrote:
This is an interesting implementation. I am curious, what are you trying to achieve that necessitates adding and removing fields? And wouldnt that be solved better with some table relationship instead?

On Tue, Jan 28, 2025 at 1:33 AM Mayank Prajapati <mayankprajapati1399@gmail.com> wrote:
I am making a full stack project with JavaScript and react for front end , Postgre SQL for database and Django for backend and Django rest framework for APIs. So in models.py file there's one field which is to be removed and another field is to be added at the end. This process has to be done once daily at specific time. For example, assume there are five fields in my models i.e. A,B,C,D and E. At some specific time field B will be removed and new field E will be added after D, again same process will repeat next day field C will be removed and new field F will be added after E. I can implement this process through python file handling and "with" method. 

So my question is, should i implement this process in my Django project? Will this process work efficiently in production environment?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/75091646-157a-4b2e-8aa0-0c05b2d50b0fn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CALHJg5%2BRzLrFE0%3DAro_ByQe3nJixBMLObdfVQNsBoeTsRibLhQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CAEn_UdWRSHSvBVtvpQ3QfENwbFtX7zA2i2p4z9_ye2vNd4Mqhg%40mail.gmail.com.

Tuesday, January 28, 2025

Re: File handling in Django

This is an interesting implementation. I am curious, what are you trying to achieve that necessitates adding and removing fields? And wouldnt that be solved better with some table relationship instead?

On Tue, Jan 28, 2025 at 1:33 AM Mayank Prajapati <mayankprajapati1399@gmail.com> wrote:
I am making a full stack project with JavaScript and react for front end , Postgre SQL for database and Django for backend and Django rest framework for APIs. So in models.py file there's one field which is to be removed and another field is to be added at the end. This process has to be done once daily at specific time. For example, assume there are five fields in my models i.e. A,B,C,D and E. At some specific time field B will be removed and new field E will be added after D, again same process will repeat next day field C will be removed and new field F will be added after E. I can implement this process through python file handling and "with" method. 

So my question is, should i implement this process in my Django project? Will this process work efficiently in production environment?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/75091646-157a-4b2e-8aa0-0c05b2d50b0fn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/django-users/CALHJg5%2BRzLrFE0%3DAro_ByQe3nJixBMLObdfVQNsBoeTsRibLhQ%40mail.gmail.com.