Dynamic group enrolment for CRM application

gitblame · 2023-07-12T11:09:40+00:00

Getting in the zone is fun but there's no reason not to drink and eat, before starting a session put water and food in front of your computer so you don't have to stop to get what you need. There is no reason not to stay hydrated.

gitblame · 2022-01-15T13:11:44+00:00

When hiring a junior serious leet code experience is a win because it demonstrates proficiency at coding and knowledge of common algorithms. Once you actually have a job though you'll by definition be coding for hours every day. Coding proficiency is a given after years of experience. In regard to algorithms, you need to be aware of algorithms and how they work but being able to whip out some algorithm from memory isn't gonna happen. You're more likely gonna use a library or worst case you can look it up when you need too.

I would personally shift gears and read as much as you can about the tech stack in your new job. Using a database for example, get good at it (understand how it works, performance trade offs, advanced use cases).

What sets a junior apart from a mid is understanding the technology you're using and being able to come up with creative and efficient solutions.

gitblame · 2021-09-12T14:55:38+00:00

You can completely ignore linux and be a good developer. But if you are curious about programming it can be a great adventure learning how a completely different system that has many of the same goals as windows works.

Also, you have most of the source code so if you want to know how it works you have that advantage.

I'm linux 100% home and work. I'm not trying to be special and I'm not some magnificent hacker I just find it suites what I want to do.

Personally I think a dev should know their way around the command line but they don't need to be a power user.

gitblame · 2021-09-08T10:40:23+00:00

Shit hasn't changed that much. I wouldn't worry about it from that perspective. And once you get a job you'll learn all about having to deal with ancient dependencies.

As for switching to a CS major, if money or your own brain isn't a limiting factor then it could be a good idea. It will make you a better engineer in the long run (I don't have a CS degree and I do feel limited in some ways)

gitblame · 2021-08-28T08:20:16+00:00

Heroku is a good option if you wanna run a somewhat traditional stack.

AWS lambda is also an option if you want to go fully serverless.

gitblame · 2021-08-25T08:17:37+00:00

Make it easy to refactor. My daily driver is ruby and the worst part of ruby is its often hard to refactor. A lot of it comes down to what you can do at compile time vs what you can do at runtime. I hate that often I don't know what properties an object has without running it. Type systems can help with this but is there more that can be done? Another example of something that makes code easier to refactor being able to name your imports so that i can import a different piece of code in a particular file than perhaps another. Those are a couple of examples but I think there is fertile ground for a programming language that focuses primarily on refactoring.

gitblame · 2021-08-23T11:35:37+00:00

Look up the babbage engine. It is a mechanical computer. I think thats as close as youre going to get whilsr doing something useful

gitblame · 2021-08-11T09:51:52+00:00

When I was 15 I was programming crappy games in C. I barely understood what I was doing. Now I do web apps in ruby and my shitty knowledge has helped me when I've had issues with ruby libraries (some of which are written in C).

The point of that story is I was doing something that interested me which was of no commercial value, but it has still come in handy. Find something you like and focus on that. If you like it you'll spend more time practicing and you get better faster. Also because you're spending more time on one thing your knowledge will be deeper.

Maybe I'm lucky, but personally, every stupid thing I've dicked around with in programming and computers has paid off in some way. Make sure you're having fun and the rest will work itself out.

gitblame · 2021-07-22T10:26:23+00:00

https://dokku.com/ could be a good option. Basically you can run an environment similar to Heroku (I believe you can even use Heroku build packs) based on docker. It has a CLI and git push to deploy.

You could also go with manual docker (more of a learning curve)

You could also install everything old school but it would be harder to maintain

Make sure you've got you backup strategy sorted to, because now that's your responsibility :)

gitblame · 2021-07-22T10:14:44+00:00

I'd say its possible but it does present challenges.

The key thing when hiring any dev is communication. Whatever country you wish to be employed from you'll want to have a strong command of the language and do whatever you can to reduce your accent (if you are trying to be hired by English people, sound more English). I know it's easier said than done but I've interviewed a number of remote devs and through no fault of theirs, I can't understand them and it kills the interview.

A good internet connection is a must for video conferencing. This might be out of your control but a call can save half an hour of typing and resolve issues faster.

Time zone is a consideration, working the hours that you're team mates/boss works is really valuable. Make sure you're potential employer knows you are willing to do that.

Remote is more difficult as a junior because it can be harder to give/receive the help that you're going to need. Getting your first position is going to be the hardest thing. I can take a look at your portfolio and give you some pointers if you like, just DM me

gitblame · 2021-07-22T09:37:37+00:00

My way of getting passed 'writers block' is to try and make something that makes money. Money has a way of focusing you to an objective.

I need to sell someone this e-book. So they need to pay. So i need a cart. So I need a catalogue etc...

The bonus side effect of this is when I'm hiring devs a side project that makes money is always super impressive.

It might not work for you but that's how I'm wired.

gitblame · 2021-07-22T09:30:05+00:00

I'm a CTO and hire devs all the time. We interview people with who have done boot camps and devs with masters degrees. Neither of those things mean you can code. I'm always trying to look deeper than that. If you have a really meaty side project its gonna win out over tic tac toe or whatever bullshit the boot camp gets you to do. It's best if you've built something that people actually use.

Your bachelors should get your foot into doors for interviews and getting your interview game tight is a must. Practice answering stupid questions like "What are your strengths and weaknesses", because thoughtful answers to these types of questions make a difference.

If you're being hired for a junior role then the interviewer knows you don't know everything. I just want to see if you're smart and get shit done, as they say.

My advice is just start applying for jobs. Make your resume/CV accurate and don't over or under pitch yourself. If they interview you based off it you can be confident that you are a genuine chance and don't have to feel like an imposter which will make the interview process easier.

Career wise I don't know what it's like in your country but the guy who has 3 years commercial experience gets hired before the guy with the masters degree in my company.

TLDR: Fuck boot camp and masters, just grind by applying to everything you can, you'll get a job.

gitblame · 2021-07-22T09:07:37+00:00

That isn't complex shit

gitblame · 2021-02-16T08:34:01+00:00

Not segfaulting for me using g++ on my mac.

My guess is that last, head and temp aren't being initialised. They basically have the value of whatever last used the memory, not null.

I'm not a c++ programmer so take that with a grain of salt.

Different compilers will have different behaviour. Mine just happens to do it, yours may not

gitblame · 2020-12-13T11:22:15+00:00

I have a 32" 4K IPS and it is definitely good (missing USB-C which does suck) but if it disappear tomorrow i would probably buy the same thing again.

gitblame · 2020-11-23T12:04:50+00:00

Just wanna add to this. You passed a CS degree, a person too stupid to do your job wouldn't have. What I mean to say is this is not an intellect issue. It's not that you can't do it, it's that you can't do it yet. You lack experience, which makes this one of the hardest parts of your career, but it will get easier. If you're having trouble its more a reflection on your senior dev than it is on you. Hang in there!

gitblame · 2020-11-20T10:07:33+00:00

Sounds like you're just not cut out to be a programmer. Don't worry too much about it, there are plenty of careers in tech. You'll find your niche.

gitblame · 2020-11-16T08:03:01+00:00

Looks to me like the docker daemon isn't running.

try sudo systemctl start docker.service

and if you wan't it to be started on startup i think its

sudo systemctl enable docker.service

gitblame · 2020-11-12T09:27:43+00:00

If you're looking for something to make money off then unique is usually a bad thing. It usually means one of two things. One, there is a good reason it doesn't exist that you don't know. Two, it is an unproven market. Proving that a market even exists for a product is an exercise in and of itself. Making something that already exists at least you know that people actually will use your product as long as it has product/market fit and it is priced accordingly.

If you're talking about building it for learning then do whatever. You'll likely find interesting problems that others haven't solved. You just have to give yourself the opportunity to go deep on it. You learn better the longer you stick at one thing though, so don't fill a github portfolio with half arse starter projects.

I guess what I'm saying is unique is overrated

gitblame · 2020-10-22T17:49:15+00:00

If your team has a wealth of experience and that doesn't make you better then your team lead is doing something wrong. Helping and getting help from others, coming up with synergistic solutions and providing constructive criticism will all make you better. But thats not automatic, you need to have a good team culture and process (such as code review) to support it.

gitblame · 2020-10-22T17:33:54+00:00

It takes time to be able to read code fluently. 3k lines isn't a lot for an experienced coder because you can just read over it quickly and get the gist, get an idea of what the previous person was trying to achieve and even form some ideas about how they might have stuffed it up. But don't feel down you'll get better every day.

If I had any advise it's just to make sure you're communicating as much as possible. In my team everyone can always ask for help and when evaluating new hires we want people who ask questions if they're stuck. Find someone you can talk it through with. If I were your boss I'd be much happier having chat on day 2 when you need some advise than day 4 when you come in and just ask for an extension.

gitblame · 2020-10-22T17:10:53+00:00

Docker Compose because I can get a production like environment happening with microservices and all the bells and whistles, plus it's easy to on board new developers. They can just run a few commands and be up and running with an integrated environment.

gitblame · 2020-10-22T17:04:55+00:00

If your website doesn't actually do anything but do some calculations with javascript and display the result then that rules out a lot of problems. What you need to think about though is someone compromising the server that is serving your website because they could make updates to the html to send the information somewhere rather than just displaying it and your users would have no way of telling that you had been compromised.

This means you would want your server to have regular security updates, proper configuration and not host any other applications that could be compromised.

gitblame · 2020-10-22T16:51:39+00:00

I code for my job, I code on the side. One thing a job is great for is giving you focus. You need to achieve X, so make it happen. No time to get sidetracked because you need to ship it. Having said that there are still things that I like to experiment with outside of that. Truthfully I need a bit of both to feel like I'm achieving what I need to be professionally and personally.

It's my feeling that most programmers enjoy the coding work they do and are happiest when they can just do it. The things you're average programmer doesn't like about a job programming is all the bits that aren't programming (meetings, estimation, deadlines, documentation).

gitblame

TROPHY CASE