Im in the same boat, 1 yesr under my belt but still just keeping my head above water. I think experience is key, and having an open 1:1 with your senior/peers to ask and learn for ongoing situations is super important.
22 karma · joined October 11, 2013
Im in the same boat, 1 yesr under my belt but still just keeping my head above water. I think experience is key, and having an open 1:1 with your senior/peers to ask and learn for ongoing situations is super important.
It very much depends on what books you're reading, if they're right for you at your current level and helping you take the next step up. it depends on if you're not just reading but also seeking for ways to engage with what you have read....there's a lot of factors.
Actively doing will always teach more than just reading, but if you read, try out, adapt, try again, then you may find more benefit.
This can annoy folks, but the straight forward truth is that integration tests cover the unit as well as the whole, so if time is limited, they should 100% be the priority as they bring more value.
That said, I love making sure that my code is well unit tested and I build TDD where I can to make that happen. Im not dismissing the value of unit tests, but when you have to make a choice, for me, Integration tests win.
If you do post some, I for one would be keen to read.
Government contracts seem to be getting it baked in now as a legal requirement as a few cases are being taken to courts.
My company have a requirement to be level AA compliant and our designers have been taking colour compatability into account.
Generally I like to skim through articles and see whats relevant etc.
In the past I worked at an insurance based company and they had a standard non-compete clause, but many left to work in other insurance companies and no issues were ever raised.
I do agree with others here that you need to sit down and really think about what type of company you want to work for and start there.
It does sound to me that this company has process issues...tickets that are too big for a sprint, manager is micro-managing instead of letting the team self-manage etc. I think the team could do with a bit of space and time to figure out what their flow is. In software development there are those who fit well into a procesa driven culture and there are others who prefer more fluid approaches. You seem like the latter.
Its an ok process, but I personally would like to change one of the sessions to be an interactive dev... give a codebase ahead of time, nothing crazy and then get them to drive a solution, be the partner and then also work through a bug. Nothing complicated, I want to see their thought process and how they work as a team. Obviously google etc should be available.
In terms of being able to compete with larger companies, thats not always the case. Maybe not in salary, but thats only part of a job. Culture, perks, and the project itself can all be draws to bring in great devs.
I'd add that my worst ever interview was a coding one, similar to what I described, but the difference was that there were 3 people sat opposite me just watching me, no talking, no chat or fun, nothing. Dont be those people!
I rarely look at a CV in depth.
That said, thats my personal way, and if you feel like completing the degree for yourself then you should.
What I prefer is using VS Code to Live Share as it makes it much easier to talk through and show what I mean or review in real time.
Its hard, but it is worth the time when two devs can work together in such a manner.
I in no way believe that Stripe had any intentions of doing anything wrong, however it is good to hold people accountable and ensure that what they do is above board. I have personal examples of companies caring very little about users data, except when they might be caught out for it.
Thanks for the article.
You're right, it is a small amount of expenditure, but I was curious as that's now escalated across entire companies!
Thats mostly it...I bring lunch in and thats the greatest expense.
Best password is a long random words password as explained by xkcd!
I would also encourage you to look into the pros and cons of PHP, as there are situations where some other language is better. Sure you can do it in PHP anyway most of the time, but you should always look for the best solution, so using PHP may cost you more time or risk security or some aspect for a specific task. I don't know what you do and PHP could be perfect for everything you do, but knowing limitations is a good thing to know anyway. Once your happy with your level of knowledge in PHP that's when I would start looking at other languages, as you never know what you'll like. I've always been fond of java/.net stuff, but I recently tried Node and I love it, so you may find other things that you enjoy coding in.
It's important to remember that PHP is not going to be suitable for every situation that you develop in and knowing what else is out there, and having a basic knowledge in how the other languages work and their pros vs cons means that you can chose the right solution at the right time. Ultimately if you want to be a PHP developer I would recommend really focusing and learning that language first and then looking further afield. After all its better to be a master of one language, with the ability to pick up new skills as needed in others, than be an amateur at 10.